From the course: Azure DevOps: Continuous Delivery with YAML Pipelines

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Continuous delivery and publishing artifacts

Continuous delivery and publishing artifacts - Azure Tutorial

From the course: Azure DevOps: Continuous Delivery with YAML Pipelines

Start my 1-month free trial

Continuous delivery and publishing artifacts

“

- [Instructor] Continuous integration refers to how code is built. It's an opportunity for developers to ensure that their code is working, and they do that by running the continuous integration builds. These simplify the automated testing and building of code, and for this reason, continuous integration jobs are usually run on every check-in of the code, just to make sure that the builds continue to work, and they're triggered whenever a code changes on the repository. The output of continuous integration jobs is known as build artifacts, and these include binaries or the executables that can be run. Continuous delivery, on the other hand, is all about taking code that has been built and then deploying it into a runtime environment. Usually including a production environment, which makes sure that all the same binaries are used in each of the different environments. We want to ensure that the targets have the code…

Contents