Azure-Pipelines Flashcards
Agent
An agent is an installable software that runs a build or deployment job.
Artifact
An artifact is a collection of files or packages published by a build. Artifacts are made available for next tasks, such as distribution or deployment.
Build
A build represents one execution of a pipeline. It collects the logs associated with running the steps and the results of running tests.
Continuous delivery
Continuous delivery (CD) (also known as Continuous Deployment) is a process by which code is built, tested, and deployed to one or more test and production stages. Deploying and testing in multiple stages helps drive quality.
Continuous integration
Continuous integration (CI) is the practice used by development teams to simplify the testing and building of code.
Automated tests and builds are run as part of the CI process.
Deployment target
A deployment target is a virtual machine, container, web app, or any service used to host the application being developed. A pipeline might deploy the app to one or more deployment targets after the build is completed and tests are run.
Job
A job represents an execution boundary of a set of steps. All the steps run together on the same agent.
A build contains one or more jobs. Most jobs run on an agent.
Pipeline
A pipeline defines the continuous integration and deployment process for your app. It’s made up of steps called tasks.
It can be thought of as a script that describes how your test, build, and deployment steps are run.
Release
When you use the visual designer, you create a release pipeline also to a build pipeline. A release is a term used to describe one execution of a release pipeline. It’s made up of deployments to multiple stages.
Stage
Stage
Stages are the primary divisions in a pipeline: “build the app,” “run integration tests,” and “deploy to user acceptance testing” are good examples of stages.
Task
A task is the building block of a pipeline. For example, a build pipeline might consist of build tasks and test tasks. A release pipeline consists of deployment tasks. Each task runs a specific job in the pipeline.
Trigger
A trigger is something that’s set up to tell the pipeline when to run. You can configure a pipeline to run upon a push to a repository at scheduled times or upon completing another build. All these actions are known as triggers.
Microsoft-hosted agents
Each time a pipeline is run, a new virtual machine (instance) is provided. The virtual machine is discarded after one use.
Self-hosted agents
An agent that you set up and manage on your own to run build and deployment jobs is a self-hosted agent.
Agent pool jobs
The most common types of jobs. The jobs run on an agent that is part of an agent pool.