FI master

Author: brcrista

CONTRIBUTING.md

@@ -0,0 +1,33 @@
+# Instructions for Contributing Code
+
+## Contributing bug fixes
+
+We are currently accepting contributions in the form of bug fixes. A bug must have an issue tracking it in the issue tracker. Your pull request should include a link to the bug that you are fixing. If you've submitted a PR for a bug, please post a comment in the bug to avoid duplication of effort.
+
+## Contributing features
+
+Features (things that add new or improved functionality) may be accepted, but will need to first be approved in the form of a suggestion issue.
+
+Design changes will not be accepted at this time. If you have a design change proposal, please log a suggestion issue.
+
+## Legal
+
+You will need to complete a Contributor License Agreement (CLA). Briefly, this agreement testifies that you are granting us permission to use the submitted change according to the terms of the project's license, and that the work being submitted is under appropriate copyright.
+
+Please submit a Contributor License Agreement (CLA) before submitting a pull request. You may visit https://cla.microsoft.com to sign digitally. 
+
+## Housekeeping
+
+Your pull request should: 
+
+* Include a description of what your change intends to do
+* Be a child commit of a reasonably recent commit in the **master** branch 
+    * Requests need not be a single commit, but should be a linear sequence of commits (i.e. no merge commits in your PR)
+* It is desirable, but not necessary, for the tests to pass at each commit
+* Have clear commit messages 
+    * e.g. "Refactor feature", "Fix issue", "Add tests for issue"
+* Include adequate tests 
+    * At least one test should fail in the absence of your non-test code changes. If your PR does not match this criteria, please specify why
+    * Tests should include reasonable permutations of the target fix/change
+    * Include baseline changes with your change
+    * All changed code must have 100% code coverage

ISSUE_TEMPLATE.md

@@ -0,0 +1,23 @@
+Please check our current Issues to see if someone already reported this https://github.com/Microsoft/azure-pipelines-task-lib/issues
+
+### Environment
+azure-pipelines-task-lib version: 
+
+### Issue Description
+<!--- Please provide a short description of the issue -->
+
+### Expected behaviour
+<!--- Tell us what should happen -->
+
+### Actual behaviour
+<!--- Tell us what happens instead -->
+
+### Steps to reproduce
+1. 
+2. 
+3. 
+4. 
+5. 
+
+### Logs
+<!-- Any logs you have/stack traces/etc. -->

README.md

@@ -1,16 +1,22 @@
 
-# VSTS DevOps Task SDK
+# Azure Pipelines Task SDK
 
-Libraries for writing [Visual Studio Team Services](https://www.visualstudio.com/en-us/products/visual-studio-team-services-vs.aspx) build and deployment tasks
+Libraries for writing [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) tasks
 
 Reference examples of our in the box tasks [are here](https://github.com/Microsoft/vsts-tasks)
 
 ## Status
+
 |   | Build & Test |
 |---|:-----:|
-|![Win](res/win_med.png) **Windows**|![Build & Test](https://mseng.visualstudio.com/DefaultCollection/_apis/public/build/definitions/b924d696-3eae-4116-8443-9a18392d8544/2553/badge?branch=master)| 
-|![Apple](res/apple_med.png) **OSX**|![Build & Test](https://mseng.visualstudio.com/_apis/public/build/definitions/b924d696-3eae-4116-8443-9a18392d8544/5471/badge?branch=master)|
-|![Ubuntu14](res/ubuntu_med.png) **Ubuntu 14.04**|![Build & Test](https://mseng.visualstudio.com/_apis/public/build/definitions/b924d696-3eae-4116-8443-9a18392d8544/4123/badge?branch=master)|
+|![Win-x64](res/win_med.png) **Windows**|[![Build & Test][win-build-badge]][build]| 
+|![macOS](res/apple_med.png) **macOS**|[![Build & Test][macOS-build-badge]][build]| 
+|![Linux-x64](res/ubuntu_med.png) **Linux**|[![Build & Test][linux-build-badge]][build]|
+
+[win-build-badge]: https://dev.azure.com/mseng/PipelineTools/_apis/build/status/azure-pipelines-task-lib-ci?branchName=master&jobname=windows
+[macOS-build-badge]: https://dev.azure.com/mseng/PipelineTools/_apis/build/status/azure-pipelines-task-lib-ci?branchName=master&jobname=macOS
+[linux-build-badge]: https://dev.azure.com/mseng/PipelineTools/_apis/build/status/azure-pipelines-task-lib-ci?branchName=master&jobname=linux
+[build]: https://dev.azure.com/mseng/PipelineTools/_build/latest?definitionId=7623
 
 ## Highlights
 
@@ -34,8 +40,12 @@ A task which automates Powershell technologies can be written with our Powershel
 
 Documentation: [PowerShell API](powershell/Docs/README.md)
 
+## Notes on authoring Tasks
+
+Starting from [version v2.141.0](https://github.com/Microsoft/azure-pipelines-agent/releases/tag/v2.141.0), the agent can now run on three OS architectures: x86, x64, and 32-bit ARM. When authoring a new task, you can check agent variable: `Agent.OSArchitecture` (possible values: X86, X64, ARM) to restrict running said task to a particular set of OS architectures.
+
 
-[npm-lib-image]: https://img.shields.io/npm/v/vsts-task-lib.svg?style=flat
-[npm-lib-url]: https://www.npmjs.com/package/vsts-task-lib
+[npm-lib-image]: https://img.shields.io/npm/v/azure-pipelines-task-lib.svg?style=flat
+[npm-lib-url]: https://www.npmjs.com/package/azure-pipelines-task-lib
 [npm-sdk-image]: https://img.shields.io/npm/v/vsts-task-sdk.svg?style=flat
 [npm-sdk-url]: https://www.npmjs.com/package/vsts-task-sdk

.vsts-ci.yml renamed to azure-pipelines.yml

@@ -2,44 +2,49 @@ trigger:
 - master
 - features/*
 
-phases:
+jobs:
 #################################################
-- phase: windows
+- job: windows
 #################################################
-  condition: and(succeeded(), eq(variables.os, 'Windows_NT'))
-  queue: Hosted VS2017
+  displayName: windows
+  pool:
+    vmImage: vs2017-win2016
 
   steps:
   ################################################################################
-  # vsts-task-lib
+  # azure-pipelines-task-lib
   ################################################################################
 
   # npm install
   - task: Npm@1
-    displayName: (vsts-task-lib) npm install
+    displayName: (azure-pipelines-task-lib) npm install
     inputs:
       command: install
       workingDir: node
 
   # use node 5
   - powershell: |
       & "$(build.sourcesDirectory)/res/UseNode5.ps1"
-    displayName: (vsts-task-lib) use node 5.10.1
+    displayName: (azure-pipelines-task-lib) use node 5.10.1
 
   # build/test
-  - script: node make.js test
+  - script: |
+      chcp 437
+      node make.js test
     workingDirectory: node
-    displayName: (vsts-task-lib) node make.js test  
+    displayName: (azure-pipelines-task-lib) node make.js test  
 
   # use node 6
   - task: NodeTool@0
-    displayName: (vsts-task-lib) use node 6.10.3
+    displayName: (azure-pipelines-task-lib) use node 6.10.3
     inputs:
       versionSpec: "6.10.3"
 
   # build/test
-  - script: node make.js test
-    displayName: (vsts-task-lib) node make.js test
+  - script: |
+      chcp 437
+      node make.js test
+    displayName: (azure-pipelines-task-lib) node make.js test
     workingDirectory: node
 
   ################################################################################
@@ -59,81 +64,83 @@ phases:
     workingDirectory: powershell
 
 #################################################
-- phase: linux
+- job: linux
 #################################################
-  condition: and(succeeded(), eq(variables.os, 'Linux'))
-  queue: Hosted Linux Preview
+  displayName: Linux
+  pool:
+    vmImage: ubuntu-16.04
 
   steps:
   ################################################################################
-  # vsts-task-lib
+  # azure-pipelines-task-lib
   ################################################################################
 
   # npm install
   - task: Npm@1
-    displayName: (vsts-task-lib) npm install
+    displayName: (azure-pipelines-task-lib) npm install
     inputs:
       command: install
       workingDir: node
 
   # use node 5
   - task: NodeTool@0
-    displayName: (vsts-task-lib) use node 5.10.1
+    displayName: (azure-pipelines-task-lib) use node 5.10.1
     inputs:
       versionSpec: "5.10.1"
 
   # build/test
   - script: node make.js test
     workingDirectory: node
-    displayName: (vsts-task-lib) node make.js test  
+    displayName: (azure-pipelines-task-lib) node make.js test  
 
   # use node 6
   - task: NodeTool@0
-    displayName: (vsts-task-lib) use node 6.10.3
+    displayName: (azure-pipelines-task-lib) use node 6.10.3
     inputs:
       versionSpec: "6.10.3"
 
   # build/test
   - script: node make.js test
-    displayName: (vsts-task-lib) node make.js test
+    displayName: (azure-pipelines-task-lib) node make.js test
     workingDirectory: node
 
 #################################################
-- phase: macOS
+- job: macOS
 #################################################
-  condition: and(succeeded(), eq(variables.os, 'Darwin'))
-  queue: Hosted macOS Preview
+  displayName: macOS
+  pool:
+    vmImage: macOS-10.13
 
   steps:
   ################################################################################
-  # vsts-task-lib
+  # azure-pipelines-task-lib
   ################################################################################
 
   # npm install
   - task: Npm@1
-    displayName: (vsts-task-lib) npm install
+    displayName: (azure-pipelines-task-lib) npm install
     inputs:
       command: install
       workingDir: node
 
   # use node 5
   - task: NodeTool@0
-    displayName: (vsts-task-lib) use node 5.10.1
+    displayName: (azure-pipelines-task-lib) use node 5.10.1
     inputs:
       versionSpec: "5.10.1"
 
   # build/test
   - script: node make.js test
     workingDirectory: node
-    displayName: (vsts-task-lib) node make.js test  
+    displayName: (azure-pipelines-task-lib) node make.js test  
 
   # use node 6
   - task: NodeTool@0
-    displayName: (vsts-task-lib) use node 6.10.3
+    displayName: (azure-pipelines-task-lib) use node 6.10.3
     inputs:
       versionSpec: "6.10.3"
 
   # build/test
   - script: node make.js test
-    displayName: (vsts-task-lib) node make.js test
+    displayName: (azure-pipelines-task-lib) node make.js test
     workingDirectory: node

node/README.md

@@ -1,31 +1,35 @@
 
-# VSTS DevOps Task SDK
+# Azure Pipelines Task SDK
 
-Libraries for writing [Visual Studio Team Services](https://www.visualstudio.com/en-us/products/visual-studio-team-services-vs.aspx) build and deployment tasks
+Libraries for writing [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines) tasks
 
-![VSTS](https://mseng.visualstudio.com/DefaultCollection/_apis/public/build/definitions/b924d696-3eae-4116-8443-9a18392d8544/2553/badge)
-
-Reference examples of our in the box tasks [are here](https://github.com/Microsoft/vsts-tasks)
+Reference examples of our in the box tasks [are here](https://github.com/Microsoft/azure-pipelines-tasks)
 
 ## TypeScript Tasks
 
 Cross platform tasks are written in TypeScript.  It is the preferred way to write tasks once.
 
 [![NPM version][npm-lib-image]][npm-lib-url]
 
-Step by Step: [Create Task](docs/stepbystep.md)  
+Step by Step: [Create Task](https://docs.microsoft.com/en-us/azure/devops/extend/develop/add-build-task?view=vsts)  
 
-Documentation: [TypeScript API](docs/vsts-task-lib.md), [task JSON schema](https://aka.ms/vsts-tasks.schema.json)
+Documentation: [TypeScript API](docs/azure-pipelines-task-lib.md), [task JSON schema](https://aka.ms/vsts-tasks.schema.json)
 
 Guidance: [Finding Files](docs/findingfiles.md), [Minimum agent version](docs/minagent.md), [Proxy](docs/proxy.md), [Certificate](docs/cert.md)
 
 ## Reference Examples
 
-The [ShellScript Task](https://github.com/Microsoft/vsts-tasks/tree/master/Tasks/ShellScript) and the [XCode Task](https://github.com/Microsoft/vsts-tasks/tree/master/Tasks/Xcode) are good examples.
+The [ShellScript Task](https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks/ShellScriptV2) and the [XCode Task](https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks/XcodeV5) are good examples.
 
 ## Contributing
 
-### Node
+We are accepting contributions and we try to stay on top of issues. 
+
+[Contribution Guide](../CONTRIBUTING.md).
+
+[Logging Issues](https://github.com/Microsoft/azure-pipelines-task-lib/issues)
+
+## Building the library
 
 Once:
 ```bash
@@ -40,11 +44,19 @@ $ npm test
 
 Set environment variable TASK_TEST_TRACE=1 to display test output.
 
-[npm-lib-image]: https://img.shields.io/npm/v/vsts-task-lib.svg?style=flat
-[npm-lib-url]: https://www.npmjs.com/package/vsts-task-lib
+[npm-lib-image]: https://img.shields.io/npm/v/azure-pipelines-task-lib.svg?style=flat
+[npm-lib-url]: https://www.npmjs.com/package/azure-pipelines-task-lib
+
+## Powershell
+
+We also maintain a PowerShell library for Windows task development.
+
+Library: [Powershell Library](../powershell)
+
+Usage: [Consuming the SDK](../powershell/Docs/Consuming.md)
 
 ## Third Party Notices
 To generate/update third party notice file run:
 ```bash
 $ node generate-third-party-notice.js
-```
+```

node/Strings/resources.resjson/en-US/resources.resjson

@@ -6,10 +6,14 @@
   "loc.messages.LIB_MkdirFailedInvalidDriveRoot": "Unable to create directory '%s'. Root directory does not exist: '%s'",
   "loc.messages.LIB_MkdirFailedInvalidShare": "Unable to create directory '%s'. Unable to verify the directory exists: '%s'. If directory is a file share, please verify the share name is correct, the share is online, and the current process has permission to access the share.",
   "loc.messages.LIB_MultilineSecret": "Secrets cannot contain multiple lines",
+  "loc.messages.LIB_ProcessError": "There was an error when attempting to execute the process '%s'. This may indicate the process failed to start. Error: %s",
+  "loc.messages.LIB_ProcessExitCode": "The process '%s' failed with exit code %s",
+  "loc.messages.LIB_ProcessStderr": "The process '%s' failed because one or more lines were written to the STDERR stream",
   "loc.messages.LIB_ReturnCode": "Return code: %d",
   "loc.messages.LIB_ResourceFileNotExist": "Resource file doesn\\'t exist: %s",
   "loc.messages.LIB_ResourceFileAlreadySet": "Resource file has already set to: %s",
   "loc.messages.LIB_ResourceFileNotSet": "Resource file haven\\'t set, can\\'t find loc string for key: %s",
+  "loc.messages.LIB_StdioNotClosed": "The STDIO streams did not close within %s seconds of the exit event from process '%s'. This may indicate a child process inherited the STDIO streams and has not yet exited.",
   "loc.messages.LIB_WhichNotFound_Linux": "Unable to locate executable file: '%s'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.",
   "loc.messages.LIB_WhichNotFound_Win": "Unable to locate executable file: '%s'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.",
   "loc.messages.LIB_LocStringNotFound": "Can\\'t find loc string for key: %s",
@@ -25,5 +29,6 @@
   "loc.messages.LIB_PathHasNullByte": "Path cannot contain null bytes",
   "loc.messages.LIB_OperationFailed": "Failed %s: %s",
   "loc.messages.LIB_UseFirstGlobMatch": "Multiple workspace matches. using first.",
-  "loc.messages.LIB_MergeTestResultNotSupported": "Merging test results from multiple files to one test run is not supported on this version of build agent for OSX/Linux, each test result file will be published as a separate test run in VSO/TFS."
+  "loc.messages.LIB_MergeTestResultNotSupported": "Merging test results from multiple files to one test run is not supported on this version of build agent for OSX/Linux, each test result file will be published as a separate test run in VSO/TFS.",
+  "loc.messages.LIB_PlatformNotSupported": "Platform not supported: %s"
 }

node/ThirdPartyNotice.txt

@@ -2,7 +2,7 @@
 THIRD-PARTY SOFTWARE NOTICES AND INFORMATION
 Do Not Translate or Localize
 
-This Visual Studio Team Services extension (vsts-task-lib) is based on or incorporates material from the projects listed below (Third Party IP). The original copyright notice and the license under which Microsoft received such Third Party IP, are set forth below. Such licenses and notices are provided for informational purposes only. Microsoft licenses the Third Party IP to you under the licensing terms for the Visual Studio Team Services extension. Microsoft reserves all other rights not expressly granted under this agreement, whether by implication, estoppel or otherwise.
+This Azure Pipelines extension (azure-pipelines-task-lib) is based on or incorporates material from the projects listed below (Third Party IP). The original copyright notice and the license under which Microsoft received such Third Party IP, are set forth below. Such licenses and notices are provided for informational purposes only. Microsoft licenses the Third Party IP to you under the licensing terms for the Visual Studio Team Services extension. Microsoft reserves all other rights not expressly granted under this agreement, whether by implication, estoppel or otherwise.
 
 1.	asap (git+https://github.com/kriskowal/asap.git)
 2.	balanced-match (git://github.com/juliangruber/balanced-match.git)

node/dependencies/typings.json

@@ -1,5 +1,5 @@
 {
-	"name": "vsts-task-lib",
+	"name": "azure-pipelines-task-lib",
 	"main": "task.d.ts",
 	"globalDependencies": {
 		"node": "registry:dt/node#6.0.0+20160709114037",