I'm wondering if anyone knows if there is a Release Calendar widget/view in Azure DevOps Services. Our support team simply wants to see our production releases (successful release pipeline runs) on a calendar so they know when updates to our service has happened.
Note: I looked through the existing widgets and marketplace but nothing stood out so asking here before we evaluate building it.
Update: We presently don't use Boards or Repos in Azure DevOps. We only use Pipelines so looking for a solution that plays nice with just that but appreciate sharing the other options.
You can use Release Pipeline Overview widget without install anything in marketplace.
After you select one release pipeline, this widget will show the names and status in the specific pipeline like below.
Then in your release pipeline, click Options and find the Release name format.
Change the Release name format and add the specifice predefined variable to it.
This variable will display the current date in you release name. Then you can get the release calendar in the Release pipeline overview widger like below.
Addition
You can refer to here to get more information about pre-defined variable to specify the format mask.
https://learn.microsoft.com/en-us/azure/devops/pipelines/release/index?view=azure-devops#how-do-i-manage-the-names-for-new-releases
I believe you can leverage the new Portfolio Plans beta stuff to accomplish this.
Related
In an Azure Devops project, I see all the "Recent" pipeline runs under the Recent tab.
The list includes pipelines not run for 16 months - as well as those run this week, for example.
How do I customise the list to show only those run in the past month (for example)?
NOTES:
I am NOT talking about the lifetime of the releases themselves, which I know can be customised in the Project Properties --> Pipelines.
I do not want to delete the old pipelines - just not see them in the "Recent" list.
It shows 50（default value） pipelines in recent tab according to our backend API test. I am afraid that you can't customise the list to show.
We've been using environments for a while now for our dev and test instances. I like being able to go to the environment and seeing the commits and work items associated with the particular build/release but can't find a way to export them. Does anyone know of a way to export the workitems?
Using environments you also loose the ability to see which build/release a ticket went out in or have I missed something?
Your first and second question, kind of, have the same answer.
In short, you don't want to be using Environments to view which work items are associated with a release.
Azure DevOps has a built-in mechanism to view work items directly within the Release or Pipelines page (Depending on whether you're using classic or YAML).
Here is a great guide published by Microsoft regarding how work pipeline-based work item linking works, as well as how to retrieve work items associated with a release:
https://devblogs.microsoft.com/premier-developer/how-to-retrieve-all-work-items-associated-with-a-release-pipeline-using-azure-devops-api/
Update:
Specifically regarding how to view linked work items in Pipelines. You'll want to look under "Related":
Clicking on "x work items" will show you the full list of work items:
I am trying to figure out how to sort artifacts in Azure DevOps. Is there a way I can view recently pushed artefact for a particular feed instead of trying to filter based on package names?
Thank you
Sorry but for now we don't support sort based on Last Pushed date. Azure Devops sorts the packages based on PackageName by default.
I'm afraid you have to use Filter and Feed button to find your package:
I think your idea is meaningful, so I add a feature request for you in User Voice Forum. You can vote for it and track the issue there, the product team would consider about it if it gets enough points.
Link here: https://developercommunity.visualstudio.com/idea/1089652/support-sorting-packages-in-azure-artifact-feed-vi.html
In my organization we recently moved to Azure DevOps and at this point we are configuring dashboards to monitor what is happening in the environments.
I would like to create a matrix widget where Y would be Release Piplelines and X would be the environments we have.
In the table I would like to have all the images that are on a particular environment at the moment.
Thank you in advance for your answer!
You can add Release pipeline overview widget to your azure devops dashboards. With this widget, you can view and track the status of a release pipeline. it shows the release as a series of environments, with the name of the release and the date or time it was started.
Go the DashBoards under Overview in your azure devops project portal. Click Edit and search for Release pipeline overview widget. Then configure the Release pipeline to be displayed on the dashboard. The widget looks like below screenshot. It might not be exactly what you want. But it is most closest one i can find in azure devops extension market.
If you would like to create your own widget. You can refer to this example provided in microsoft official site
If you want to view and track the status of multiple Release pipelines. You can add multiple Release pipeline overview widgets one for each of them.
Please check here to explore more other widgets. Hope above helps!
In Jira, you can create Releases for a project. As part of a Release, you can specify which issues are part of it as well as add Release notes.
These are extremely useful when you have automated build scripts, as the API for JIRA can be queried by the scripts as part of a CD pipeline.
You can therefore do things like (but not limited to):
Fill in a changelog dynamically
Stop deployment if there are an issues part of the Release that are not Done
Retrieve version numbers
Question: Is there a VSTS equivalent?
I do not think there is currently anything directly comparable to a Jira 'release' built into Azure Devops, which would allow you to package up completed Work Items on a board into a 'Release' work item.
You could implement a "poor man's" version of this by creating a custom process for your project that included a new 'Release' work item type. Each 'Release work item' could then be manually linked to work items you want to include in that release and could contain custom fields for the 'version' number or any other meta data you wanted to store with that release. This could then later be queried from a CD pipeline which, taking one of your examples, would allow you to do something like iterate over the linked work items for the release and make sure they are in a 'done' status.
Edit: As an example of integration techniques, the REST API for Azure DevOps supports a simple REST GET request to query all work items in a project for a custom work item type:
GET https://dev.azure.com/{organization}/{project}/_apis/wit/reporting/workitemrevisions?types={YourCustomWorkItemType}&includeLatestOnly=true&api-version=4.1
The API will also return any custom fields you have associated with this WIT, listing them under the key 'Custom.{YourFieldName}' within the "fields" object of the WIT response.
If your team was working with sprints, the other potential method I could think of to do this would be for each 'sprint' to become a named version which would become your 'release' once the sprint was complete. Work items that were not implemented as part of that sprint/version/release) would then be moved into the next sprint or closed. I'm not sure this approach would be very sustainable for complex projects.
There are features of interest listed on the Azure Devops Features Timeline that may improve this workflow in the near future (for example, "Release traceability – Work Item integration", planned for implementation in 2018 Q4), although it's difficult to find out any implementation details.