Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Steps are a linear sequence of operations that make up a job.
steps: [ task | script | powershell | pwsh | bash | checkout | download | downloadBuild | getPackage | publish | template | reviewApp ] # Steps are a linear sequence of operations that make up a job.
steps: [ task | script | powershell | pwsh | bash | checkout | download | downloadBuild | publish | template ] # Steps are a linear sequence of operations that make up a job.
Definitions that reference this definition: pipeline, jobs.job, preDeployHook, deployHook, routeTrafficHook, postRouteTrafficHook, onFailureHook, onSuccessHook
Type | Description |
---|---|
steps.task | Runs a task. |
steps.script | Runs a script using cmd.exe on Windows and Bash on other platforms. |
steps.powershell | Runs a script using either Windows PowerShell (on Windows) or pwsh (Linux and macOS). |
steps.pwsh | Runs a script in PowerShell Core on Windows, macOS, and Linux. |
steps.bash | Runs a script in Bash on Windows, macOS, and Linux. |
steps.checkout | Configure how the pipeline checks out source code. |
steps.download | Downloads artifacts associated with the current run or from another Azure Pipeline that is associated as a pipeline resource. |
steps.downloadBuild | Downloads build artifacts. |
steps.getPackage | Downloads a package from a package management feed in Azure Artifacts or Azure DevOps Server. |
steps.publish | Publishes (uploads) a file or folder as a pipeline artifact that other jobs and pipelines can consume. |
steps.template | Define a set of steps in one file and use it multiple times in another file. |
steps.reviewApp | Downloads creates a resource dynamically under a deploy phase provider. |
Type | Description |
---|---|
steps.task | Runs a task. |
steps.script | Runs a script using cmd.exe on Windows and Bash on other platforms. |
steps.powershell | Runs a script using either Windows PowerShell (on Windows) or pwsh (Linux and macOS). |
steps.pwsh | Runs a script in PowerShell Core on Windows, macOS, and Linux. |
steps.bash | Runs a script in Bash on Windows, macOS, and Linux. |
steps.checkout | Configure how the pipeline checks out source code. |
steps.download | Downloads artifacts associated with the current run or from another Azure Pipeline that is associated as a pipeline resource. |
steps.downloadBuild | Downloads build artifacts. |
steps.publish | Publishes (uploads) a file or folder as a pipeline artifact that other jobs and pipelines can consume. |
steps.template | Define a set of steps in one file and use it multiple times in another file. |
Each step runs in its own process on an agent and has access to the pipeline workspace on a local hard drive. This behavior means environment variables aren't preserved between steps but file system changes are.
All tasks and steps support a set of common properties, such as enabled
and env
,in addition to their task or step specific properties. For more information on configuring these properties, see Task control options and Task environment variables.
steps:
- script: echo This runs in the default shell on any machine
- bash: |
echo This multiline script always runs in Bash.
echo Even on Windows machines!
- pwsh: |
Write-Host "This multiline script always runs in PowerShell Core."
Write-Host "Even on non-Windows machines!"
Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register now