Implement CI in Azure

source

Agent

When your build or deployment runs, the system begins one or more jobs. An agent is installable software that runs a build or deployment job.

Artifact

An artifact is a collection of files or packages published by abuild. Artifacts are made available for the tasks, such as distribution or deployment.

Build

Represents on execution of a pipeline. It collects the logs associated with running the steps and the test results.

Job

A build contains one or more jobs. Most jobs run on an agent. A job represents an execution boundary of a set of steps. All the steps run together on the same 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

Release is one execution of a release pipeline. It’s made up of deployments to multiple stages.

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 and test tasks. A release pipeline consists of deployment tasks. Each task runs a specific job in the pipeline.

Continuos Integration (CI)

Continuous integration (CI) is the process of automating the build and testing of code every time a team member commits changes to version control.

Continuous integration relies on four key elements for successful implementation: a Version Control System, Package Management System, Continuous Integration System, and an Automated Build Process.