Simple Pipeline<\/p>\n
\r\n Build -> Tests(QA) -> Deployment(Prod)\r\n<\/pre>\nTrigger – One which starts an action. On Commit it should trigger a pipeline
\n Stage – Pipeline contains multiple stages. Stages are logical boundaries. Build, Test and Deployment above are all stages
\n Job – Stage contains multiple jobs. Build stage contains multiple jobs like asking for VM agent, Copying Target file to drop location
\n Steps – Job contains multiple steps. Steps can be a task or script which would be run.<\/p>\nAgents would be used to build artifacts in the pipeline. Agents may be based on windows, Linux or mac images which would be available on the fly when the build stage is started during pipeline execution<\/p>\n
\r\ntrigger:\r\n- master\r\n\r\npool:\r\n vmImage: ubuntu-latest\r\n\r\nstages:\r\n- stage: Build\r\n jobs:\r\n - job: build\r\n steps:\r\n - script: \r\n echo Displayed from Script\r\n - task: Npm@1\r\n inputs:\r\n command: 'install' \r\n<\/pre>\nStages<\/strong> <\/p>\n
\r\nstages:\r\n- stage: string # name of the stage, A-Z, a-z, 0-9, and underscore\r\n displayName: string # friendly name to display in the UI\r\n dependsOn: string | [ string ]\r\n condition: string\r\n pool: string | pool\r\n variables: { string: string } | [ variable | variableReference ] \r\n jobs: [ job | templateReference]\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"Simple Pipeline Build -> Tests(QA) -> Deployment(Prod) Trigger – One which starts an action. On Commit it should trigger a pipeline Stage – Pipeline contains multiple stages. Stages are logical boundaries. Build, Test and Deployment above are all stages Job – Stage contains multiple jobs. Build stage contains multiple jobs like asking for VM agent,… Continue reading