• A trigger tells a Pipeline to run. It could be CI or Scheduled, manual(if not specified), or after another build finishes.
• A pipeline is made up of one or more stages. A pipeline can deploy to one or more environments.
• A stage organizes jobs in a pipeline, and each stage can have one or more jobs.
• Each job runs on one agent, such as Ubuntu, Windows, macOS, etc. A job can also be agentless.
• Each agent runs a job that contains one or more steps.
• A step can be a task or script and is the smallest building block of a pipeline.
• A task is a pre-packaged script that acts, such as invoking a REST API or publishing a build artifact.
• An artifact is a collection of files or packages published by a run.

• Recreate, Canary, Ring based, Rolling Update, A/B Deloyment, Feature Flag etc

Isolated placeholder in a repository can be categorized into Local, pre-release, Release, etc. Once your Artifacts are deployed to one environment, you promote them to another view so that they can be deployed in another environment, with that view being the trigger. Could you explain with the help of an example?

Any other limitations of Microsoft-hosted agents?

Multistage Docker Build

FROM node:18-alpine AS installer
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
RUN npm run build
FROM nginx:latest AS deployer
COPY --from=installer /app/build /usr/share/nginx/html

Check out this repo and Day15 Video

• Azure Key Vault and access via a variable group
• Runtime variable, tokenize your files and replace token step inside the pipeline
• Third-party secret management service such as Hashicorp Vault

Pick up the issue you have faced while doing hands-on on Azure DevOps if you have followed this series or any other resource.

Structure your answer in STAR format

S: Situation

T: Task

A: Action

R: Result

• Check out Video 10 for ACI and Video 11 for Kubernetes