# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
# THE SOFTWARE.
explanation.introduction=While subversion allows you to specify the \u2018--password\u2019option explicitly in the command line, this is generally not desirable when you are using Jenkins, because:
reason.1=People can read your password by using <tt>pargs</tt>.
reason.2=Password will be stored in a clear text in Jenkins.
alternative.introduction=A preferable approach is to do the following steps:
step.1=Logon to the server that runs Jenkins, by using the same user account Jenkins uses.
step.2=Manually run <tt>svn co ...</tt>
step.3=Subversion asks you the password interactively. Type in the password.
step.4=Subversion stores it in its authentication cache, and for successive <tt>svn co ...</tt> it will use the password stored in the cache.
final.words=Note that this approach still doesn\u2019t really make your password secure, it just makes it a bit harder to read.
reason.2=Adgangskoden vil blive gemt i klartekst i Jenkins.
explanation.introduction=\
Mens subversion tillader at du specificerer ''--password'' parameteren p\u00e5 kommandolinjen er dette ikke generelt \u00f8nskv\u00e6rdigt n\u00e5r du bruger Jenkins, da:
alternative.introduction=En foretrukket tilgang er f\u00f8lgende:
step.4=Subversion gemmer det i sit forh\u00e5ndsgodkendelsesmellemlager og for efterf\u00f8lgende <tt>svn co ...</tt> vil den mellemlagrede adgangskode blive benyttet.
explanation.introduction=Bien que Subversion vous permette de passer l''option '--password' en clair dans la ligne de commande, ça n''est en général pas souhaitable quand vous utilisez Jenkins. En effet:
reason.1=On peut lire votre mot de passe en utilisant <tt>pargs</tt>;
reason.2=Votre mot de passe sera enregistré en clair dans Jenkins
alternative.introduction=Une meilleure approche est de suivre les étapes suivantes:
step.1=Se logguer sur le serveur qui fait tourner Jenkins, en utilisant le même compte utilisateur que Jenkins;
step.2=Lancer manuellement <tt>svn co ...</tt>;
step.3=Subversion vous demande votre mot de passe de façon intéractive. Tapez votre mot de passe;
step.4=Subversion le stocke dans son cache d''authentification; pour les demandes <tt>svn co ...</tt> futures, il utilisera le mot de passe de son cache.
final.words=Notez bien que cette approche ne rend pas votre mot de passe complètement sécurisé; il devient simplement un peu plus difficile à lire.
step.4=Subversion\u306F\u30D1\u30B9\u30EF\u30FC\u30C9\u3092\u30AD\u30E3\u30C3\u30B7\u30E5\u3057\u3001\u6B21\u306E<tt>svn co ...</tt>\u3067\u30AD\u30E3\u30C3\u30B7\u30E5\u3055\u308C\u305F\u30D1\u30B9\u30EF\u30FC\u30C9\u3092\u4F7F\u7528\u3057\u307E\u3059\u3002
# Password will be stored in a clear text in Jenkins.
reason.2=Senha ser\u00e1 armazenada num campo de texto do Jenkins
# While subversion allows you to specify the ''--password'' option explicitly in the command line, this is generally not desirable when you are using Jenkins, because:
explanation.introduction=Enquanto Subversion permite especificar a op\u00e7\u00e3o '--password'' explicitamente, na linha de comando, esse modo n\u00e3o \u00e9 desej\u00e1vel no Jenkins.
# A preferable approach is to do the following steps:
alternative.introduction=Uma abordagem prefer\u00edvel seria realizar os seguintes passos:
# Subversion stores it in its authentication cache, and for successive <tt>svn co ...</tt> it will use the password stored in the cache.
step.4=Subversion armazena a senha num cache que pode ser recuperada por <tt>svn co ...</tt>.
step.4=Subversion \u6703\u628a\u5bc6\u78bc\u5b58\u5728\u9a57\u8b49\u5feb\u53d6\u4e2d\uff0c\u5f8c\u7e8c\u7684<tt>svn co ...</tt> \u5c31\u6703\u4f7f\u7528\u5feb\u53d6\u5bc6\u78bc\u3002
