Skip to main content

Azure DevOps release pipeline capabilities


Azure DevOps has extended support for pipelines as code (also called YAML pipelines) for continuous deployment and started introducing various release management capabilities into pipelines as code.


Feature

YAML

Classic Build

Classic Release

Notes

Agents

Yes

Yes

Yes

Specifies a required resource on which the pipeline runs.

Approvals

Yes

No

Yes

Defines a set of validations required before completing a deployment stage.

Artifacts

Yes

Yes

Yes

Supports publishing or consuming different package types.

Caching

Yes

Yes

No

Reduces build time by allowing outputs or downloaded dependencies from one run to be reused in later runs. In Preview, available with Azure Pipelines only.

Conditions

Yes

Yes

Yes

Specifies conditions to be met before running a job.

Container jobs

Yes

No

No

Specifies jobs to run in a container.

Demands

Yes

Yes

Yes

Ensures pipeline requirements are met before running a pipeline stage. Requires self-hosted agents.

Dependencies

Yes

Yes

Yes

Specifies a requirement that must be met to run the next job or stage.

Deployment groups

Yes

No

Yes

Defines a logical set of deployment target machines.

Deployment group jobs

No

No

Yes

Specifies a job to release to a deployment group.

Deployment jobs

Yes

No

No

Defines the deployment steps. Requires Multi-stage pipelines experience.

Environment

Yes

No

No

Represents a collection of resources targeted for deployment. Available with Azure Pipelines only.

Gates

No

No

Yes

Supports automatic collection and evaluation of external health signals before completing a release stage. Available with Azure Pipelines only.

Jobs

Yes

Yes

Yes

Defines the execution sequence of a set of steps.

Service connections

Yes

Yes

Yes

Enables a connection to a remote service that is required to execute tasks in a job.

Service containers

Yes

No

No

Enables you to manage the lifecycle of a containerized service.

Stages

Yes

No

Yes

Organizes jobs within a pipeline.

Task groups

No

Yes

Yes

Encapsulates a sequence of tasks into a single reusable task. If using YAML, see templates.

Tasks

Yes

Yes

Yes

Defines the building blocks that make up a pipeline.

Templates

Yes

No

No

Defines reusable content, logic, and parameters.

Triggers

Yes

Yes

Yes

Defines the event that causes a pipeline to run.

Variables

Yes

Yes

Yes

Represents a value to be replaced by data to pass to the pipeline.

Variable groups

Yes

Yes

Yes

Use to store values that you want to control and make available across multiple pipelines.



Labels:

Comments

Post a Comment

Popular posts from this blog

What is release, and what is a deployment?

T o understand the concepts and the technical implementation in many tools, you need to know how tool vendors define the difference between a release and a deployment. A  release  is a package or container containing a versioned set of artifacts specified in a release pipeline in your CI/CD process. It also includes a snapshot of all the information required to carry out all the tasks and activities in a release pipeline, such as: The stages or environments. The tasks for each one. The values of task parameters and variables. The release policies such as triggers, approvers, and release queuing options. On the other hand,  Deployment  is the action of running the tasks for one stage, which results in a tested and deployed application and other activities specified for that stage. Starting a release starts each deployment based on the settings and policies defined in the original release pipeline. There can be multiple deployments of each release, even for one stage. ...
Post a Comment
Read more

Enable Trace on Dynamcis 365 on premise using PowerShell

Enable trace settings through Windows PowerShell Note These changes made in Windows PowerShell do not update the Registry. These changes update the DeploymentProperties and ServerSettingsProperties tables in the MSCRM_CONFIG database. Register the cmdlets 1.      Log in to the administrator account on your Microsoft Dynamics CRM server. 2.      In a Windows PowerShell window, type the following command: Add-PSSnapin Microsoft.Crm.PowerShell To obtain a list of the current settings, type the following command: Get-CrmSetting TraceSettings Set the trace settings 1.      Type the following command: $setting = Get-CrmSetting TraceSettings 2.      Type the following command to enable tracing: $setting.Enabled=$True 3.      Type the following command to set the trace settings: Set-CrmSetting $setting 4.      Type the following command...
Post a Comment
Read more

Delivery cadence and three types of triggers

Both the release and stages make use of triggers. There are three types of triggers we recognize. Continuous deployment trigger You can set up this trigger on your release pipeline. Once you do that, your release pipeline will trigger every time a build completes, and a new release will be created. Scheduled triggers This speaks for itself, but it allows you to set up a time-based manner to start a new release—for example, every night at 3:00 AM or 12:00 PM. You can have one or multiple schedules per day, but it will always run at this specific time. Manual trigger With a manual trigger, a person or system triggers the release based on a specific event. When it's a person, it probably uses some UI to start a new release. When it's an automated process, some events will likely occur. You can trigger the release from another system using the automation engine   Navigation Traditional IT deployment cycle What is Continuous Delivery? What is release, and what is a deployment? Azure...
Post a Comment
Read more