提交 5188b26a 编写于 作者: D Daniel Beck

[FIX JENKINS-22867] Fix localization and relative links.

上级 016f304c
<?jelly escape-by-default='true'?>
<j:jelly xmlns:j="jelly:core" xmlns:l="/lib/layout">
<l:ajax>
<l:ajax>
<div>
<p>
For projects that use Maven as the build system. This causes Jenkins to
invoke Maven with the given goals and options. A non-zero exit code from
Maven makes Jenkins mark the build as a failure.
Some Maven versions have a bug where it doesn't return the exit code correctly.
</p>
<p>
Jenkins passes <a href="${rootURL}/env-vars.html" target="_new">
various environment variables</a> to Maven, which you can access from Maven as "${env.VARIABLENAME}".
</p>
<p>
The same variables can be used in command-line arguments (as if you are invoking this from shell).
For example, you can specify <tt>-DresultsFile=${WORKSPACE}/${BUILD_TAG}.results.txt</tt>
</p>
<p>
${%para1}
</p>
<p>
${%para2(rootURL)}
</p>
<p>
${%para3}
</p>
</div>
</l:ajax>
</l:ajax>
</j:jelly>
para1=For projects that use Maven as the build system. This causes Jenkins to invoke \
Maven with the given goals and options. A non-zero exit code from Maven makes Jenkins \
mark the build as a failure. Some Maven versions have a bug where it doesn't return \
the exit code correctly.
para2=Jenkins passes <a href="{0}/env-vars.html" target="_new">various environment \
variables</a> to Maven, which you can access from Maven as "$&#123;env.VARIABLENAME}".
para3=The same variables can be used in command-line arguments (as if you are invoking \
this from shell). For example, you can specify \
<tt>-DresultsFile=\$&#123;WORKSPACE}/\$&#123;BUILD_TAG}.results.txt</tt>
<?xml version="1.0" encoding="UTF-8"?>
<?jelly escape-by-default='true'?>
<j:jelly xmlns:j="jelly:core" xmlns:l="/lib/layout">
<l:ajax>
<div>
<p>
Für Projekte, die Maven als Build-System benutzen. Dies veranlasst Jenkins,
Maven mit den Angegebenen Zielen (goals) und Optionen aufzurufen. Ein Ergebniscode
ungleich 0 bewirkt, dass Jenkins den Build als Fehlschlag markiert.
Mache Versionen von Maven beinhalten einen Fehler, durch den der Ergebniscode
nicht immer korrekt zurückgeliefert wird.
</p>
<p>
Jenkins übergibt <a href="../../env-vars.html">
zahlreiche Umgebungsvariablen</a> an Maven, auf die Sie innerhalb Mavens mittels "${env.VARIABLENAME}" zugreifen können.
</p>
<p>
Die gleichen Umgebungsvariablen können in Kommandozeilenargumenten verwendet werden (genauso als ob Sie
Kommandos in einer Shell ausführen würden), wie beispielsweise
<tt>-DresultsFile=${WORKSPACE}/${BUILD_TAG}.results.txt</tt>
</p>
</div>
</l:ajax>
</j:jelly>
para1=F\u00fcr Projekte, die Maven als Build-System benutzen. Dies veranlasst Jenkins, \
Maven mit den Angegebenen Zielen (goals) und Optionen aufzurufen. Ein Ergebniscode \
ungleich 0 bewirkt, dass Jenkins den Build als Fehlschlag markiert. \
Mache Versionen von Maven beinhalten einen Fehler, durch den der Ergebniscode \
nicht immer korrekt zur\u00fcckgeliefert wird.
para2=Jenkins \u00fcbergibt <a href="{0}/env-vars.html">\
zahlreiche Umgebungsvariablen</a> an Maven, auf die Sie innerhalb Mavens mittels "$&#123;env.VARIABLENAME}" zugreifen k\u00f6nnen.
para3=Die gleichen Umgebungsvariablen k\u00f6nnen in Kommandozeilenargumenten verwendet werden (genauso als ob Sie \
Kommandos in einer Shell ausf\u00fchren w\u00fcrden), wie beispielsweise \
<tt>-DresultsFile=$&#123;WORKSPACE}/$&#123;BUILD_TAG}.results.txt</tt>
\ No newline at end of file
<?xml version="1.0" encoding="UTF-8"?>
<?jelly escape-by-default='true'?>
<j:jelly xmlns:j="jelly:core" xmlns:l="/lib/layout">
<l:ajax>
<div>
<p>
Pour les projets qui utilisent Maven comme outil de build.
Jenkins invoquera Maven avec les cibles et les options spécificiées.
Un code de retour différent de zéro indique à Jenkins que le build doit
être marqué comme un échec.
Certaines versions de Maven ont un bug qui ne permet pas le retour correct
d'un code de sortie.
</p>
<p>
Jenkins passe <a href="../../env-vars.html">
certaines variables d'environment</a> à Maven, auxquelles vous pouvez
accéder à l'aide de "${env.NOMDEVARIABLE}".
</p>
<p>
Les mêmes variables peuvent être utilisées comme des arguments de ligne
de commande, comme si vous faisiez une invocation à partir d'un Shell.
Par exemple, vous pouvez spécifier <tt>-DresultsFile=${WORKSPACE}/${BUILD_TAG}.results.txt</tt>
</p>
</div>
</l:ajax>
</j:jelly>
para1=Pour les projets qui utilisent Maven comme outil de build. \
Jenkins invoquera Maven avec les cibles et les options sp\u00e9cifici\u00e9es. \
Un code de retour diff\u00e9rent de z\u00e9ro indique \u00e0 Jenkins que le build doit \
\u00eatre marqu\u00e9 comme un \u00e9chec. \
Certaines versions de Maven ont un bug qui ne permet pas le retour correct \
d'un code de sortie.
para2=Jenkins passe <a href="{0}/env-vars.html">\
certaines variables d'environment</a> \u00e0 Maven, auxquelles vous pouvez \
acc\u00e9der \u00e0 l'aide de "$&#123;env.NOMDEVARIABLE}".
para3=Les m\u00eames variables peuvent \u00eatre utilis\u00e9es comme des arguments de ligne \
de commande, comme si vous faisiez une invocation \u00e0 partir d'un Shell. \
Par exemple, vous pouvez sp\u00e9cifier <tt>-DresultsFile=$&#123;WORKSPACE}/$&#123;BUILD_TAG}.results.txt</tt>
<?xml version="1.0" encoding="UTF-8"?>
<?jelly escape-by-default='true'?>
<j:jelly xmlns:j="jelly:core" xmlns:l="/lib/layout">
<l:ajax>
<div>
<p>
ビルドシステムとしてMavenを使用するプロジェクト向けです。
Jenkinsは、与えられたゴールとオプションとともにMavenを起動します。
Mavenが0でない終了コードを返すと、Jenkinsはビルドが失敗したと判断します。
Mavenのあるバージョンは、終了コードを適切に返さないバグがあります。
</p>
<p>
Jenkinsは、<a href="../../env-vars.html" target="_new">
利用可能な環境変数</a> をMavenに渡します。Mavenでは"${env.VARIABLENAME}"として参照できます。
</p>
<p>
同じ変数を、コマンドラインの引数で使用することができます(シェルから起動しているかのように)。
例えば、<tt>-DresultsFile=${WORKSPACE}/${BUILD_TAG}.results.txt</tt>のように指定できます。
</p>
</div>
</l:ajax>
</j:jelly>
para1=\u30d3\u30eb\u30c9\u30b7\u30b9\u30c6\u30e0\u3068\u3057\u3066Maven\u3092\u4f7f\u7528\u3059\u308b\u30d7\u30ed\u30b8\u30a7\u30af\u30c8\u5411\u3051\u3067\u3059\u3002\
Jenkins\u306f\u3001\u4e0e\u3048\u3089\u308c\u305f\u30b4\u30fc\u30eb\u3068\u30aa\u30d7\u30b7\u30e7\u30f3\u3068\u3068\u3082\u306bMaven\u3092\u8d77\u52d5\u3057\u307e\u3059\u3002\
Maven\u304c0\u3067\u306a\u3044\u7d42\u4e86\u30b3\u30fc\u30c9\u3092\u8fd4\u3059\u3068\u3001Jenkins\u306f\u30d3\u30eb\u30c9\u304c\u5931\u6557\u3057\u305f\u3068\u5224\u65ad\u3057\u307e\u3059\u3002\
Maven\u306e\u3042\u308b\u30d0\u30fc\u30b8\u30e7\u30f3\u306f\u3001\u7d42\u4e86\u30b3\u30fc\u30c9\u3092\u9069\u5207\u306b\u8fd4\u3055\u306a\u3044\u30d0\u30b0\u304c\u3042\u308a\u307e\u3059\u3002
para2=Jenkins\u306f\u3001<a href="{0}/env-vars.html" target="_new">\
\u5229\u7528\u53ef\u80fd\u306a\u74b0\u5883\u5909\u6570</a> \u3092Maven\u306b\u6e21\u3057\u307e\u3059\u3002Maven\u3067\u306f"$&#123;env.VARIABLENAME}"\u3068\u3057\u3066\u53c2\u7167\u3067\u304d\u307e\u3059\u3002
para3=\u540c\u3058\u5909\u6570\u3092\u3001\u30b3\u30de\u30f3\u30c9\u30e9\u30a4\u30f3\u306e\u5f15\u6570\u3067\u4f7f\u7528\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059(\u30b7\u30a7\u30eb\u304b\u3089\u8d77\u52d5\u3057\u3066\u3044\u308b\u304b\u306e\u3088\u3046\u306b)\u3002\
\u4f8b\u3048\u3070\u3001<tt>-DresultsFile=$&#123;WORKSPACE}/$&#123;BUILD_TAG}.results.txt</tt>\u306e\u3088\u3046\u306b\u6307\u5b9a\u3067\u304d\u307e\u3059\u3002
<?xml version="1.0" encoding="UTF-8"?>
<?jelly escape-by-default='true'?>
<j:jelly xmlns:j="jelly:core" xmlns:l="/lib/layout">
<l:ajax>
<div>
<p>
Para projetos que usam Maven como sistema de constru&#231;&#227;o. Isto faz o Jenkins
invocar o Maven com os objetivos e op&#231;&#245;es informadas. Um c&#243;digo de sa&#237;da
diferente de zero vindo do Maven faz com que o Jenkins marque a constru&#231;&#227;o como uma falha.
Algumas vers&#245;es do Maven t&#234;m um bug onde ele n&#227;o retorna o c&#243;digo de sa&#237;da corretamente.
</p>
<p>
O Jenkins passa <a href="../../env-vars.html">
v&#225;rias vari&#225;veis de ambiente</a> para o Maven, que voc&#234; pode acessar do Maven como "${env.VARIABLENAME}".
</p>
<p>
As mesmas vari&#225;veis podem ser usadas como argumentos na linha de comando (como se voc&#234; fosse invocar do shell).
Por exemplo, voc&#234; pode especificar <tt>-DresultsFile=${WORKSPACE}/${BUILD_TAG}.resultados.txt</tt>
</p>
</div>
</l:ajax>
</j:jelly>
para1=Para projetos que usam Maven como sistema de constru&#231;&#227;o. Isto faz o Jenkins \
invocar o Maven com os objetivos e op&#231;&#245;es informadas. Um c&#243;digo de sa&#237;da \
diferente de zero vindo do Maven faz com que o Jenkins marque a constru&#231;&#227;o como uma falha. \
Algumas vers&#245;es do Maven t&#234;m um bug onde ele n&#227;o retorna o c&#243;digo de sa&#237;da corretamente.
para2=O Jenkins passa <a href="{0}/env-vars.html">\
v&#225;rias vari&#225;veis de ambiente</a> para o Maven, que voc&#234; pode acessar do Maven como "$&#123;env.VARIABLENAME}".
para3=As mesmas vari&#225;veis podem ser usadas como argumentos na linha de comando (como se voc&#234; fosse invocar do shell). \
Por exemplo, voc&#234; pode especificar <tt>-DresultsFile=$&#123;WORKSPACE}/$&#123;BUILD_TAG}.resultados.txt</tt>
<?xml version="1.0" encoding="UTF-8"?>
<?jelly escape-by-default='true'?>
<j:jelly xmlns:j="jelly:core" xmlns:l="/lib/layout">
<l:ajax>
<div>
<p>
Для проектов, использующих сборочную систему Maven. Эта настройка укажет Jenkins
вызывать Maven с данными целями и опциями. Если Maven завершит работу с
ненулевым кодом, сборка будет считаться провалившейся. Некоторые версии Maven
содержат ошибку, возвращая неверный код по завершении.
</p>
<p>
Jenkins передает <a href="../../env-vars.html">
различные переменные окружения</a> в Maven, которые можно использовать с помощью
синтаксической конструкции Maven "${env.VARIABLENAME}".
</p>
<p>
Эти же переменные можно использовать и в командной строке (еcли вы вызываете
Maven из сценария shell). Например, вы можете указать
<tt>-DresultsFile=${WORKSPACE}/${BUILD_TAG}.results.txt</tt>.
</p>
</div>
</l:ajax>
</j:jelly>
para1=\u0414\u043b\u044f \u043f\u0440\u043e\u0435\u043a\u0442\u043e\u0432, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0449\u0438\u0445 \u0441\u0431\u043e\u0440\u043e\u0447\u043d\u0443\u044e \u0441\u0438\u0441\u0442\u0435\u043c\u0443 Maven. \u042d\u0442\u0430 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0443\u043a\u0430\u0436\u0435\u0442 Jenkins \
\u0432\u044b\u0437\u044b\u0432\u0430\u0442\u044c Maven \u0441 \u0434\u0430\u043d\u043d\u044b\u043c\u0438 \u0446\u0435\u043b\u044f\u043c\u0438 \u0438 \u043e\u043f\u0446\u0438\u044f\u043c\u0438. \u0415\u0441\u043b\u0438 Maven \u0437\u0430\u0432\u0435\u0440\u0448\u0438\u0442 \u0440\u0430\u0431\u043e\u0442\u0443 \u0441 \
\u043d\u0435\u043d\u0443\u043b\u0435\u0432\u044b\u043c \u043a\u043e\u0434\u043e\u043c, \u0441\u0431\u043e\u0440\u043a\u0430 \u0431\u0443\u0434\u0435\u0442 \u0441\u0447\u0438\u0442\u0430\u0442\u044c\u0441\u044f \u043f\u0440\u043e\u0432\u0430\u043b\u0438\u0432\u0448\u0435\u0439\u0441\u044f. \u041d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 Maven \
\u0441\u043e\u0434\u0435\u0440\u0436\u0430\u0442 \u043e\u0448\u0438\u0431\u043a\u0443, \u0432\u043e\u0437\u0432\u0440\u0430\u0449\u0430\u044f \u043d\u0435\u0432\u0435\u0440\u043d\u044b\u0439 \u043a\u043e\u0434 \u043f\u043e \u0437\u0430\u0432\u0435\u0440\u0448\u0435\u043d\u0438\u0438.
para2=Jenkins \u043f\u0435\u0440\u0435\u0434\u0430\u0435\u0442 <a href="{0}/env-vars.html">\
\u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0435 \u043f\u0435\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0435 \u043e\u043a\u0440\u0443\u0436\u0435\u043d\u0438\u044f</a> \u0432 Maven, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0436\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e\
\u0441\u0438\u043d\u0442\u0430\u043a\u0441\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u043a\u043e\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u0438 Maven "$&#123;env.VARIABLENAME}".
para3=\u042d\u0442\u0438 \u0436\u0435 \u043f\u0435\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0435 \u043c\u043e\u0436\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0438 \u0432 \u043a\u043e\u043c\u0430\u043d\u0434\u043d\u043e\u0439 \u0441\u0442\u0440\u043e\u043a\u0435 (\u0435c\u043b\u0438 \u0432\u044b \u0432\u044b\u0437\u044b\u0432\u0430\u0435\u0442\u0435 \
Maven \u0438\u0437 \u0441\u0446\u0435\u043d\u0430\u0440\u0438\u044f shell). \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u0432\u044b \u043c\u043e\u0436\u0435\u0442\u0435 \u0443\u043a\u0430\u0437\u0430\u0442\u044c \
<tt>-DresultsFile=$&#123;WORKSPACE}/$&#123;BUILD_TAG}.results.txt</tt>.
<?xml version="1.0" encoding="UTF-8"?>
<?jelly escape-by-default='true'?>
<j:jelly xmlns:j="jelly:core" xmlns:l="/lib/layout">
<l:ajax>
<div>
<p>
Yap&#305;land&#305;rma sistemi olarak Maven kullanan projeler i&#231;in kullan&#305;l&#305;r. Bununla Jenkins
i&#231;erisinde, Maven'&#305;, verilen hedefler ve se&#231;enekler ile &#231;al&#305;&#351;t&#305;rabilirsiniz. Maven'dan gelen
0 olmayan(non-zero) &#231;&#305;k&#305;&#351; kodu, yap&#305;land&#305;rmay&#305; ba&#351;ar&#305;s&#305;z olarak ilan eder.
para1=Yap&#305;land&#305;rma sistemi olarak Maven kullanan projeler i&#231;in kullan&#305;l&#305;r. Bununla Jenkins \
i&#231;erisinde, Maven'&#305;, verilen hedefler ve se&#231;enekler ile &#231;al&#305;&#351;t&#305;rabilirsiniz. Maven'dan gelen \
0 olmayan(non-zero) &#231;&#305;k&#305;&#351; kodu, yap&#305;land&#305;rmay&#305; ba&#351;ar&#305;s&#305;z olarak ilan eder. \
Baz&#305; Maven versiyonlar&#305;nda &#231;&#305;k&#305;&#351; kodunun d&#252;zg&#252;n d&#246;nememesi gibi bir bug vard&#305;r.
</p>
<p>
Jenkins <a href="../../env-vars.html">
&#231;e&#351;itli ortam de&#287;i&#351;kinlerini</a> Maven'a aktar&#305;r, bunlara Maven i&#231;erisinden "${env.VARIABLENAME}" ile ula&#351;abilirsiniz.
</p>
<p>
Ayn&#305; de&#287;i&#351;kenleri komut sat&#305;r&#305;nda parametre olarak kullanabilirsiniz (bunu shell'den &#231;a&#287;&#305;r&#305;yorsan&#305;z)
Mesela, <tt>-DresultsFile=${WORKSPACE}/${BUILD_TAG}.results.txt</tt> &#351;eklinde belirleyebilirsiniz.
</p>
</div>
</l:ajax>
</j:jelly>
para2=Jenkins <a href="{0}/env-vars.html">\
&#231;e&#351;itli ortam de&#287;i&#351;kinlerini</a> Maven'a aktar&#305;r, bunlara Maven i&#231;erisinden "$&#123;env.VARIABLENAME}" ile ula&#351;abilirsiniz.
para3=Ayn&#305; de&#287;i&#351;kenleri komut sat&#305;r&#305;nda parametre olarak kullanabilirsiniz (bunu shell'den &#231;a&#287;&#305;r&#305;yorsan&#305;z) \
Mesela, <tt>-DresultsFile=$&#123;WORKSPACE}/$&#123;BUILD_TAG}.results.txt</tt> &#351;eklinde belirleyebilirsiniz
<?xml version="1.0" encoding="UTF-8"?>
<?jelly escape-by-default='true'?>
<j:jelly xmlns:j="jelly:core" xmlns:l="/lib/layout">
<l:ajax>
<div>
<p>
適用以 Maven 建置的專案,讓 Jenkins 使用指定的 Goal 及選項叫用 Maven。
Jenkins 會將 Maven 任何非 0 的結束代碼都視為建置失敗。
某些版本的 Maven 有 Bug,不會回傳正確的結束代碼。
</p>
<p>
Jenkins 傳送<a href="../../env-vars.html" target="_new">多個環境變數</a>
Maven,您可以在 Maven 裡用 "${env.VARIABLENAME}" 來取得變數值。
</p>
<p>
同樣的變數也可以用在命令列參數裡 (假設您是從 Shell 叫用)。
例如: <code>-DresultsFile=${WORKSPACE}/${BUILD_TAG}.results.txt</code>
</p>
</div>
</l:ajax>
</j:jelly>
para1=\u9069\u7528\u4ee5 Maven \u5efa\u7f6e\u7684\u5c08\u6848\uff0c\u8b93 Jenkins \u4f7f\u7528\u6307\u5b9a\u7684 Goal \u53ca\u9078\u9805\u53eb\u7528 Maven\u3002\
Jenkins \u6703\u5c07 Maven \u4efb\u4f55\u975e 0 \u7684\u7d50\u675f\u4ee3\u78bc\u90fd\u8996\u70ba\u5efa\u7f6e\u5931\u6557\u3002\
\u67d0\u4e9b\u7248\u672c\u7684 Maven \u6709 Bug\uff0c\u4e0d\u6703\u56de\u50b3\u6b63\u78ba\u7684\u7d50\u675f\u4ee3\u78bc\u3002
para2=Jenkins \u50b3\u9001<a href="{0}/env-vars.html" target="_new">\u591a\u500b\u74b0\u5883\u8b8a\u6578</a>\u7d66 \
Maven\uff0c\u60a8\u53ef\u4ee5\u5728 Maven \u88e1\u7528 "$&#123;env.VARIABLENAME}" \u4f86\u53d6\u5f97\u8b8a\u6578\u503c\u3002
para3=\u540c\u6a23\u7684\u8b8a\u6578\u4e5f\u53ef\u4ee5\u7528\u5728\u547d\u4ee4\u5217\u53c3\u6578\u88e1 (\u5047\u8a2d\u60a8\u662f\u5f9e Shell \u53eb\u7528)\u3002\
\u4f8b\u5982: <code>-DresultsFile=$&#123;WORKSPACE}/$&#123;BUILD_TAG}.results.txt</code>\u3002
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册