If like many other people you are confused about the below settings of the Classic Release Pipelines in Azure DevOps, look no further. Today we are going to clarify this once and for all.
In this article I'm going to cover these 5 infamous confusing settings of Azure Pipelines:
- Report deployment status to the repository host
- Report deployment status to Work
- Report deployment status to Boards
- Report deployment status to Jira
- Enable the deployment status badge
Today's topic has been highly requested through the comments on my videos and posts, and on some of the social media platforms I'm in. And by the way if you are not following me, go below and check the links to my platforms.
Video
As usual, if you are a visual learner, or simply prefer to watch and listen instead of reading, here you have the video with the whole explanation and demo, which to be fair is much more complete than this post.
Link to the video: https://youtu.be/EHbPpQNoBvI
If you rather prefer reading, well... let's just continue :)
Where?
First off, let's see where to find them.
Just go to your Classic Release Pipelines, and open a Pipeline.
Click on Edit, then Options, and finally Integrations. And here you have those 5 infamous options.
Ok, with that out of the way, let's go deep now in every single setting.
Report deployment status to the repository host
If your sources are in an Azure Repos Git repository in your project, this option displays a badge on the Azure Repos pages.
The badge indicates where the specific commit got deployed and whether the deployment is passing or failing.
This as you can imagine can be helpful to have a snapshot of your deployment status directly in the repo.
Watch the video here for a full demo of this setting (starts at minute 1:41)
Let's see the next two options, which are probably the most confusing ones because at a first glance they seem to be basically the same. But, in fact, they are fairly different.
Report deployment status to Work
The Report deployment status to Work allows you link the Release runs (with the status) to your Work Items in the "Links" section:
It can be beneficial for reporting purposes, or if you export your Work Items in other formats. However, I would not recommend using this one (see the next options) because it doesn't offer an immediate visualization in the work item itself
Watch the video here for a full demo of this setting (starts at minute 3:39)
Report deployment status to Boards
This setting is similar to the previous one, but it offers a much better and clearer UI. In fact, Deployments are linked to the Work Items in the Deployments Section:
Not only, clicking on each deployment box you can gather more information on the deployment itself.
When you enable this option, you'd have to map your custom deployment stages to predefined ones (Development, Staging, Test, Production, Unmapped).
Watch the video here for a full demo of this setting (starts at minute 5:46)
Hope the difference between those 2 options is clearer now. I think both can be useful, depending on your work style.
Report deployment status to Jira
Finally, let's check the remaining 2 options.
This Report deployment status to Jira option is similar to the previous one, and in fact the same mapping applies. However, as the name says, the link is done with cards in Jira rather than with work items in Azure Boards
Watch the video here for a full demo of this setting (starts at minute 8:29)
Enable the deployment status badge
Finally, the easier one. What this setting does is providing a link for each Release stage selected.
Each link, in return, represents a badge like this one which can be added to your Readme.md files in GitHub, a website or basically anywhere you want to have a visualization of the status of your deployment:
Watch the video here for a full demo of this setting (starts at minute 9:13)
Conclusions
Now the Release Pipelines in Azure DevOps don't have secrets for us... well there's actually more to cover, but I will leave that to another post/video.
Let me know in the comment section below if this explanation was good, and if you have now a better understanding of the platform.
Like, share and follow me 🚀 for more content:
📽 YouTube
☕ Buy me a coffee
💖 Patreon
🌐 CoderDave.io Website
👕 Merch
👦🏻 Facebook page
🐱💻 GitHub
👲🏻 Twitter
👴🏻 LinkedIn
🔉 Podcast
Top comments (2)
Thank you! I'm dealing with tracking changes through differents environments and this is very helpful
Glad to be helpful :) Thanks for the feedback