Difference between revisions of "Deployment:"
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
condition: string | condition: string | ||
continueOnError: boolean # 'true' if future jobs should run even if this job fails; defaults to 'false' | continueOnError: boolean # 'true' if future jobs should run even if this job fails; defaults to 'false' | ||
− | container: containerReference # | + | container: containerReference # Container to run this job inside |
services: { string: string | container } # container resources to run as a service container | services: { string: string | container } # container resources to run as a service container | ||
timeoutInMinutes: nonEmptyString # how long to run the job before automatically cancelling | timeoutInMinutes: nonEmptyString # how long to run the job before automatically cancelling |
Revision as of 12:55, 3 March 2022
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/deployment-jobs?view=azure-devops
jobs: - deployment: string # Name of the deployment. The word "deploy" is a keyword and is unsupported as the deployment name. displayName: string # friendly name to display in the UI pool: # not required for virtual machine resources name: string # Use only global level variables. Stage/job level variables are not supported to define pool name. demands: string | [ string ] workspace: clean: outputs | resources | all # what to clean up before the job runs dependsOn: string condition: string continueOnError: boolean # 'true' if future jobs should run even if this job fails; defaults to 'false' container: containerReference # Container to run this job inside services: { string: string | container } # container resources to run as a service container timeoutInMinutes: nonEmptyString # how long to run the job before automatically cancelling cancelTimeoutInMinutes: nonEmptyString # how much time to give 'run always even if cancelled tasks' before killing them variables: # several syntaxes, see specific section environment: string # target environment name and optionally a resource name to record the deployment history; format: <environment-name>.<resource-name> strategy: runOnce: #rolling, canary are the other strategies that are supported deploy: steps: [ script | bash | pwsh | powershell | checkout | task | templateReference ]
Related
See also
- Azure Pipelines:
az pipelines
,trigger:, stages:
,variables:, parameters:,
inputs:
,group:
,template:
,jobs:
,job:
,steps:
,dependsOn:
,task:
,condition:
,resources:
,pool:
,stage:
,extends:
,deployment:, scriptType:, inlineScript:, repositories:, pr:, repository:, type:
, Default Azure Pipeline, Azure Pipeline Library, Azure Pipeline Job full syntax
Advertising: