microsoft · davidstaheli · Sep 22, 2018 · Sep 19, 2018 · Sep 22, 2018 · Sep 22, 2018
diff --git a/README.md b/README.md
@@ -1,8 +1,8 @@
-# Visual Studio Team Services Tasks
+# Azure Pipelines tasks
 ![Tasks](/taskbanner.png "Tasks")
 
 ## Overview
-This repo contains the tasks that are provided out-of-the-box with Visual Studio Team Services and Team Foundation Server.
+This repo contains the tasks that are provided out-of-the-box with Azure Pipelines and Team Foundation Server.
 
 This provides open examples on how we write tasks which will help you write other tasks which can be uploaded to your account or server.  See **Writing Tasks** below.
 
@@ -30,11 +30,11 @@ See the documentation for [Continuous integration and deployment](https://aka.ms
 
 If you need custom functionality in your build/release, it is usually simpler to use the existing script running tasks such as the PowerShell or Shell Script tasks.  Writing a new task may be appropriate if you need deeper integration or reusability in many build definitions
 
-Tasks are simply tool runners.  They know how to run MSBuild, VSTest, etc... in a first class way and handle return codes, how to treat std/err out, and how to write timeline records based on expected output.  They also get access to credentials to write back to TFS/Team Services. 
+Tasks are simply tool runners.  They know how to run MSBuild, VSTest, etc... in a first class way and handle return codes, how to treat std/err out, and how to write timeline records based on expected output.  They also get access to credentials to write back to TFS/Azure Pipelines. 
 
-For uploading custom tasks to VSTS use the [TFS Cross Platform Command Line utility](https://github.com/Microsoft/tfs-cli).
+For uploading custom tasks to Azure Pipelines use the [TFS Cross Platform Command Line utility](https://github.com/Microsoft/tfs-cli).
 
-Tasks can also be deployed with a Visual Studio Team Services extension. See [this tutorial](https://docs.microsoft.com/en-us/vsts/extend/develop/add-build-task) for how to package tasks inside an extension.
+Tasks can also be deployed with an Azure DevOps extension. See [this tutorial](https://docs.microsoft.com/en-us/vsts/extend/develop/add-build-task) for how to package tasks inside an extension.
 
 ## Contributing
 We take contributions.  [Read here](docs/contribute.md) how to contribute.
@@ -1,4 +1,4 @@
-# Build your code using Ant in VSTS
+# Build your code using Ant in Azure Pipelines
 
 ### Parameters for Ant build task are explained below
 
@@ -9,23 +9,23 @@
 - **Target(s) :** Provide The task(s) for Ant to execute for this build. To know more [click here](https://ant.apache.org/manual/targets.html#targets)
 
 #### JUnit Test Results
-Use the next three options to manage your JUnit test results in VSTS
+Use the next three options to manage your JUnit test results in Azure Pipelines
 
-- **Publish to VSTS/TFS :** Select this option to publish JUnit Test results produced by the Ant build to Visual Studio Team Services/TFS. Each test result file matching `Test Results Files` will be published as a test run in VSTS.
+- **Publish to Azure Pipelines/TFS :** Select this option to publish JUnit Test results produced by the Ant build to Azure Pipelines/TFS. Each test result file matching `Test Results Files` will be published as a test run in Azure Pipelines.
 
 - **Test Results Files :** This option will appear if you select the above option. Here, provide Test results files path. Wildcards can be used. For example, `**/TEST-*.xml` for all xml files whose name starts with `TEST-."`
 
-- **Test Run Title :** This option will appear if you select the `Publish to VSTS/TFS` option. Here provide a name for the Test Run
+- **Test Run Title :** This option will appear if you select the `Publish to Azure Pipelines/TFS` option. Here provide a name for the Test Run
 
 #### Advanced
 Use the next options to manage your `ANT_HOME` and `JAVA_HOME` attributes
 
 - **Set ANT_HOME Path :** If set, overrides any existing `ANT_HOME` environment variable with the given path.
 
-- **Set JAVA_HOME by :** Select to set `JAVA_HOME` either by providing a path or let VSTS set the `JAVA_HOME` based on JDK version choosen. By default it is set to `JDK Version`
+- **Set JAVA_HOME by :** Select to set `JAVA_HOME` either by providing a path or let Azure Pipelines set the `JAVA_HOME` based on JDK version choosen. By default it is set to `JDK Version`
 
 - **JDK Version/Path :** Here provide the PATH to `JAVA_HOME` if you want to set it by path or select the appropriate JDK version.
 
 - **JDK Architecture :** Select the approriate JDK Architecture. By default it is set to `x86`
 
-**We are discontinuing the support of automated Code Coverage report generation for Ant projects starting Sprint 107 deployment of VSTS and for Team Foundation Server “15”. Please enable Code Coverage in your Ant build.xml file manually.**
+**We are discontinuing the support of automated Code Coverage report generation for Ant projects starting Sprint 107 deployment of Azure Pipelines and for Team Foundation Server “15”. Please enable Code Coverage in your Ant build.xml file manually.**
@@ -12,8 +12,8 @@
   "loc.input.help.options": "Geben Sie die Optionen an, die an die Ant-Befehlszeile übergeben werden sollen. Sie können Ihre eigenen Eigenschaften angeben (z. B. \"***-DmyProperty=meinEigenschaftenWert***\") und auch integrierte Variablen verwenden (z. B. \"***-DcollectionId=$(system.collectionId)***\"). Alternativ werden die integrierten Variablen bereits als Umgebungsvariablen während des Builds festgelegt und können direkt übergeben werden (z. B. \"***-DcollectionIdAsEnvVar=%SYSTEM_COLLECTIONID%***\").",
   "loc.input.label.targets": "Ziel(e)",
   "loc.input.help.targets": "Eine optionale, durch Leerzeichen getrennte Liste der zu erstellenden Ziele. Wenn keine Angabe erfolgt, wird das \"Standardziel\" verwendet. Wenn kein \"Standardziel\" definiert ist, wird Ant 1.6.0 verwendet, und alle Tasks auf oberster Ebene werden später erstellt.",
-  "loc.input.label.publishJUnitResults": "In TFS/Team Services veröffentlichen",
-  "loc.input.help.publishJUnitResults": "Wählen Sie diese Option aus, um vom Ant-Build generierte JUnit-Testergebnisse in TFS/Team Services zu veröffentlichen. Jede Testergebnisdatei, die mit \"Testergebnisdateien\" übereinstimmt, wird als Testlauf in TFS/Team Services veröffentlicht.",
+  "loc.input.label.publishJUnitResults": "In Azure Pipelines/TFS veröffentlichen",
+  "loc.input.help.publishJUnitResults": "Wählen Sie diese Option aus, um vom Ant-Build generierte JUnit-Testergebnisse in Azure Pipelines/TFS zu veröffentlichen. Jede Testergebnisdatei, die mit \"Testergebnisdateien\" übereinstimmt, wird als Testlauf in Azure Pipelines/TFS veröffentlicht.",
   "loc.input.label.testResultsFiles": "Testergebnisdateien",
   "loc.input.help.testResultsFiles": "Der Pfad der Testergebnisdateien. Platzhalter können verwendet werden. Beispiel: \"**/TEST-*.xml\" für alle XML-Dateien, deren Name mit \"TEST-\" beginnt.",
   "loc.input.label.testRunTitle": "Testlauftitel",

@@ -12,8 +12,8 @@
   "loc.input.help.options": "Provide any options to pass to the Ant command line. You can provide your own properties (for example, ***-DmyProperty=myPropertyValue***) and also use built-in variables (for example, ***-DcollectionId=$(system.collectionId)***). Alternatively, the built-in variables are already set as environment variables during the build and can be passed directly (for example, ***-DcollectionIdAsEnvVar=%SYSTEM_COLLECTIONID%***).",
   "loc.input.label.targets": "Target(s)",
   "loc.input.help.targets": "An optional, space-separated list of targets to build. If not specified, the `default` target will be used. If no `default` target is defined, Ant 1.6.0 and later will build all top-level tasks.",
-  "loc.input.label.publishJUnitResults": "Publish to TFS/Team Services",
-  "loc.input.help.publishJUnitResults": "Select this option to publish JUnit test results produced by the Ant build to TFS/Team Services. Each test results file matching `Test Results Files` will be published as a test run in TFS/Team Services.",
+  "loc.input.label.publishJUnitResults": "Publish to Azure Pipelines/TFS",
+  "loc.input.help.publishJUnitResults": "Select this option to publish JUnit test results produced by the Ant build to Azure Pipelines/TFS. Each test results file matching `Test Results Files` will be published as a test run in Azure Pipelines/TFS.",
   "loc.input.label.testResultsFiles": "Test results files",
   "loc.input.help.testResultsFiles": "Test results files path. Wildcards can be used ([more information](https://go.microsoft.com/fwlink/?linkid=856077)). For example, `**/TEST-*.xml` for all XML files whose name starts with TEST-.",
   "loc.input.label.testRunTitle": "Test run title",

@@ -12,8 +12,8 @@
   "loc.input.help.options": "Proporcione las opciones que se van a pasar a la línea de comandos de Ant. Puede proporcionar sus propiedades (por ejemplo, ***-DmyProperty=myPropertyValue***) y también usar variables integradas (por ejemplo, ***-DcollectionId=$(system.collectionId)***). Puede que las variables integradas ya se hayan establecido como variables de entorno durante la compilación y se puedan pasar directamente (por ejemplo, ***-DcollectionIdAsEnvVar=%SYSTEM_COLLECTIONID%***).",
   "loc.input.label.targets": "Destinos",
   "loc.input.help.targets": "Una lista opcional y separada por espacios de los destinos que se van a compilar. Si no se especifica, se usará el destino \"predeterminado\". Si no se define ningún destino \"predeterminado\", Ant 1.6.0 y las versiones posteriores compilarán todas las tareas de nivel superior.",
-  "loc.input.label.publishJUnitResults": "Publicar en TFS/Team Services",
-  "loc.input.help.publishJUnitResults": "Seleccione esta opción para publicar en TFS/Team Services los resultados de pruebas JUnit generados por la compilación de Ant. Cada archivo de resultados de pruebas que coincida con \"Archivos de resultados de pruebas\" se publicará como una serie de pruebas en TFS/Team Services.",
+  "loc.input.label.publishJUnitResults": "Publicar en Azure Pipelines/TFS",
+  "loc.input.help.publishJUnitResults": "Seleccione esta opción para publicar en Azure Pipelines/TFS los resultados de pruebas JUnit generados por la compilación de Ant. Cada archivo de resultados de pruebas que coincida con \"Archivos de resultados de pruebas\" se publicará como una serie de pruebas en Azure Pipelines/TFS.",
   "loc.input.label.testResultsFiles": "Archivos de resultados de pruebas",
   "loc.input.help.testResultsFiles": "Ruta de acceso a los archivos de resultados de pruebas. Se pueden usar caracteres comodín. Por ejemplo, \"**/TEST-*.xml\" para todos los archivos XML cuyos nombres empiecen por TEST-.",
   "loc.input.label.testRunTitle": "Título de la serie de pruebas",

@@ -12,8 +12,8 @@
   "loc.input.help.options": "Indiquez les options à passer à la ligne de commande Ant. Vous pouvez fournir vos propres propriétés (par exemple ***-DmyProperty=myPropertyValue***), et utiliser les variables intégrées (par exemple ***-DcollectionId=$(system.collectionId)***). Sinon, les variables intégrées sont déjà définies comme variables d'environnement durant la génération et peuvent être passées directement (par exemple ***-DcollectionIdAsEnvVar=%SYSTEM_COLLECTIONID%***).",
   "loc.input.label.targets": "Cible(s)",
   "loc.input.help.targets": "Liste facultative de cibles à générer, séparées par des espaces. Si rien n'est spécifié, la cible 'default' est utilisée. Si aucune cible 'default' n'est définie, Ant 1.6.0 ou ultérieur génère des tâches qui sont toutes de niveau supérieur.",
-  "loc.input.label.publishJUnitResults": "Publier sur TFS/Team Services",
-  "loc.input.help.publishJUnitResults": "Sélectionnez cette option pour publier les résultats des tests JUnit produits par la build Ant sur TFS/Team Services. Chaque fichier de résultats des tests correspondant aux 'Fichiers des résultats des tests' est publié comme série de tests sur TFS/Team Services.",
+  "loc.input.label.publishJUnitResults": "Publier sur Azure Pipelines/TFS",
+  "loc.input.help.publishJUnitResults": "Sélectionnez cette option pour publier les résultats des tests JUnit produits par la build Ant sur Azure Pipelines/TFS. Chaque fichier de résultats des tests correspondant aux 'Fichiers des résultats des tests' est publié comme série de tests sur Azure Pipelines/TFS.",
   "loc.input.label.testResultsFiles": "Fichiers de résultats des tests",
   "loc.input.help.testResultsFiles": "Chemin des fichiers de résultats des tests. Les caractères génériques sont autorisés. Par exemple, '**/TEST-*.xml' correspond à tous les fichiers XML dont le nom commence par TEST-.",
   "loc.input.label.testRunTitle": "Titre de la série de tests",

@@ -12,8 +12,8 @@
   "loc.input.help.options": "Consente di specificare tutte le opzioni da passare alla riga di comando di Ant. È possibile specificare proprietà personalizzate (ad esempio ***-DmyProperty=myPropertyValue***) e usare variabili predefinite (ad esempio ***-DcollectionId=$(system.collectionId)***). In alternativa, le variabili predefinite vengono già impostate come variabili di ambiente durante la compilazione e possono essere passate direttamente (ad esempio ***-DcollectionIdAsEnvVar=%SYSTEM_COLLECTIONID%***).",
   "loc.input.label.targets": "Destinazione/i",
   "loc.input.help.targets": "Elenco facoltativo di destinazioni per la compilazione separate da virgole. Se non viene specificato, verrà usata la destinazione `default`. Se non è definita alcuna destinazione `default`, Ant 1.6.0 o versioni successiva compilerà tutte le attività di primo livello.",
-  "loc.input.label.publishJUnitResults": "Pubblica in TFS/Team Services",
-  "loc.input.help.publishJUnitResults": "Selezionare questa opzione per pubblicare i risultati del test JUnit prodotti dalla compilazione Ant in TFS/Team Services. Ogni file dei risultati del test corrispondente al valore di `File dei risultati del test` verrà pubblicato come esecuzione dei test in TFS/Team Services.",
+  "loc.input.label.publishJUnitResults": "Pubblica in Azure Pipelines/TFS",
+  "loc.input.help.publishJUnitResults": "Selezionare questa opzione per pubblicare i risultati del test JUnit prodotti dalla compilazione Ant in Azure Pipelines/TFS. Ogni file dei risultati del test corrispondente al valore di `File dei risultati del test` verrà pubblicato come esecuzione dei test in Azure Pipelines/TFS.",
   "loc.input.label.testResultsFiles": "File dei risultati del test",
   "loc.input.help.testResultsFiles": "Percorso dei file dei risultati del test. È possibile usare i caratteri jolly, ad esempio `**/TEST-*.xml` per individuare tutti i file XML il cui nome inizia con TEST-.",
   "loc.input.label.testRunTitle": "Titolo dell'esecuzione dei test",

@@ -12,8 +12,8 @@
   "loc.input.help.options": "Ant コマンド ラインに渡すオプションを指定します。独自のプロパティ (たとえば、***-DmyProperty=myPropertyValue***) を指定することも、ビルトイン変数 (たとえば、***-DcollectionId=$(system.collectionId)***) を使用することもできます。あるいは、ビルトイン変数はビルド中は既に環境変数として設定されているため、直接渡すことができます (たとえば、***-DcollectionIdAsEnvVar=%SYSTEM_COLLECTIONID%***)。",
   "loc.input.label.targets": "ターゲット",
   "loc.input.help.targets": "作成するターゲットのオプションのスペース区切り一覧。指定しない場合、`既定` のターゲットが使用されます。`既定` のターゲットが定義されていない場合は、Ant 1.6.0 以降で最上位レベルのすべてのタスクが作成されます。",
-  "loc.input.label.publishJUnitResults": "TFS/Team Services に発行する",
-  "loc.input.help.publishJUnitResults": "Ant のビルドによって生成された JUnit のテスト結果を TFS/Team Services に発行するには、このオプションを選びます。`テスト結果ファイル` と一致する各テスト結果ファイルが、TFS/Team Services のテストの実行として発行されます。",
+  "loc.input.label.publishJUnitResults": "Azure Pipelines/TFS に発行する",
+  "loc.input.help.publishJUnitResults": "Ant のビルドによって生成された JUnit のテスト結果を Azure Pipelines/TFS に発行するには、このオプションを選びます。`テスト結果ファイル` と一致する各テスト結果ファイルが、Azure Pipelines/TFS のテストの実行として発行されます。",
   "loc.input.label.testResultsFiles": "テスト結果ファイル",
   "loc.input.help.testResultsFiles": "テスト結果ファイルのパス。ワイルドカードを使用できます。たとえば、名前が TEST- で始まるすべての XML ファイルの場合は `**/TEST-*.xml` です。",
   "loc.input.label.testRunTitle": "テストの実行のタイトル",

@@ -12,8 +12,8 @@
   "loc.input.help.options": "Ant 명령줄에 전달할 옵션을 지정하세요. 고유한 속성을 지정할 수도 있고(예: ***-DmyProperty=myPropertyValue***) 기본 제공 변수를 사용할 수도 있습니다(예: ***-DcollectionId=$(system.collectionId)***). 또는 기본 제공 변수가 빌드 중 이미 환경 변수로 설정되어 직접 전달될 수도 있습니다(예: ***-DcollectionIdAsEnvVar=%SYSTEM_COLLECTIONID%***).",
   "loc.input.label.targets": "대상",
   "loc.input.help.targets": "빌드할 대상의 공백으로 구분된 목록입니다(선택 사항). 지정되지 않은 경우 `기본` 대상이 사용됩니다. `기본` 대상이 정의되지 않은 경우 Ant 1.6.0 이상에서 모든 최상위 작업을 빌드합니다.",
-  "loc.input.label.publishJUnitResults": "TFS/Team Services에 게시",
-  "loc.input.help.publishJUnitResults": "Ant 빌드에서 생성된 JUnit 테스트 결과를 TFS/Team Services에 게시하려면 이 옵션을 선택하세요. `테스트 결과 파일`과 일치하는 각 테스트 결과 파일이 TFS/Team Services에서 테스트 실행으로 게시됩니다.",
+  "loc.input.label.publishJUnitResults": "Azure Pipelines/TFS에 게시",
+  "loc.input.help.publishJUnitResults": "Ant 빌드에서 생성된 JUnit 테스트 결과를 Azure Pipelines/TFS에 게시하려면 이 옵션을 선택하세요. `테스트 결과 파일`과 일치하는 각 테스트 결과 파일이 Azure Pipelines/TFS에서 테스트 실행으로 게시됩니다.",
   "loc.input.label.testResultsFiles": "테스트 결과 파일",
   "loc.input.help.testResultsFiles": "테스트 결과 파일 경로입니다. 와일드카드를 사용할 수 있습니다. 예를 들어, 이름이 TEST-로 시작하는 모든 XML 파일을 표시하기 위해 `**/TEST-*.xml`을 사용할 수 있습니다.",
   "loc.input.label.testRunTitle": "테스트 실행 제목",