Note that the ability to automatically create releases is available for only some artifact sources. For more information, see Continuous deployment triggers. You can configure new releases to be automatically created whenever a new version of an artifact is produced. Some of the features that depend on the linking of artifacts to a release pipeline are:Īuto-trigger releases. In this case, when you create a release, you specify individual versions for each of these sources.Īrtifacts are central to a number of features in Azure Pipelines. As you deploy the release to various stages, you will be deploying and validating the same artifacts in all stages.Ī single release pipeline can be linked to multiple artifact sources, of which one is the primary source. A release is fundamentally defined by the versioned artifacts that make up the release. When creating a release, you specify the exact version of these artifact sources for example, the number of a build coming from Azure Pipelines, or the version of a build coming from a Jenkins project.Īfter a release is created, you cannot change these versions. For example, you might link an Azure Pipelines build pipeline or a Jenkins project to your release pipeline. When authoring a release pipeline, you link the appropriate artifact sources to your release pipeline. Azure Pipelines can deploy artifacts that are produced by a wide range of artifact sources, and stored in different types of artifact repositories. An artifact is a deployable component of your application. To understand artifacts in YAML pipelines, see artifacts.Ī release is a collection of artifacts in your DevOps CI/CD processes.
This topic covers classic release pipelines.
0 kommentar(er)
