The new pipeline experience with the multi-stage pipeline feature is pretty neat, but is lacking some tracking and statistics features that are available using the classic release pipelines.
Are there any plans to support those with the YAML pipelines?
Deployments are not reported to work items
Deployment stats are not measured
You can go to Azure DevOps Feature Timeline to check what Features are under development as Shayki Abramczyk mentioned.
For these features that are not available and not under development currently. You can always submit user voices for these features to Microsoft Development team.
You properly can find some similar features requests are already submitted. You can vote up on the existing feature requests(eg. Link each stage of a YAML pipeline to work items), Or you can also submit new feature requests for your own.
Related
How do I customize the "Pipeline" tab in Azure Devps (Image 1) so that it is renamed to "Builds" (Image 2)?
Rename “Pipelines” to “Builds” in ADO
Sorry for any inconvenience.
This behavior is by designed and is not an issue. There is no way to fix it at present.
Azure devops team working on an updated user experience to manage our pipelines. These updates make the pipelines experience modern and consistent with the direction of Azure DevOps.
Moreover, these updates bring together classic build pipelines and multi-stage YAML pipelines into a single experience. It is mobile-friendly and brings various improvements to how you manage your pipelines.
You could check the document Azure DevOps Pipelines – Multi-Stage Pipelines and YAML for Continuous Delivery for some more details.
Since Multi-Stage Pipelines and YAML for Continuous Delivery introduced, Builds are no longer just a single build as before, but also include the CD part. At this time, Builds are no longer suitable as tabs, so they are changed to Pipelines.
This is a modification of product update progress.
Can someone recommend Help/Service Desk management system which works good with Azure DevOps?
We already have Azure Devops for code management with ci cd and test suites.
I am also considering JIRA service desk management, however thinking a bit scpetical in the lines of having two similar eco systems.
In next few months, we forsee potential clients who makes use of our IT services and would like to support them using service desk management.
Thank you.
By reference to this doc: What features and services do I get with Azure DevOps?, Azure DevOps provide Boards service including Agile process, Basic Process, Scrum process and CMMI process, which is easily sharing information and track the status of work, tasks, issues, or code defects. See: Azure DevOps Labs for details.
In addition, if you use Slack, you can use the Azure Boards app for Slack to create work items and monitor work item activity in your Azure Boards project from your Slack channel. If you use Microsoft Teams, you can use the Azure Boards app for Microsoft Teams to create work items and monitor work item activity in your Azure Boards project from your Teams channel. And Jira, Zappier, Service Now and so on.
BTW, if you use other management system like TeamSupport Help Desk, you could use Microsoft Power Platform to create automated workflows.
After investigation, we found that currently Azure DevOps has no service desk feature, I found a suggestion ticket in Developer community. You can vote and follow this ticket. You can also create a new suggestion ticket here. The product group will review these tickets regularly, and consider take it as roadmap.
BTW, I found this thread: https://www.reddit.com/r/azuredevops/comments/cbkxwz/azure_devops_as_a_help_desk_ticket_system/, which provides several choices, you could check it.
I create a multi-stage pipeline in YML file including build stage and deployment to dev, test and production.
I ant to have a dashboard to show me the status of deployment and which release version was deployed to each stages?
I check the "Deployment Status" widget, but it only work with release option.
So anybody has experience to support me?
I am afraid that there are no out-of-the-box widgets to display the stages of the YAML pipeline and the status of each stage on the azure devops dashboard. Currently, the Release Pipeline Overview widget accomplishes this but it cannot be linked to a YAML pipeline.
Until now, in our official feature suggestion for Azure Devops forum, there has been a such suggestion exist in it: ADO Dashboard Widget-Release Pipeline Overview should support YAML Pipelines. You can add your vote directly at the above linked feedback. Voting helps increase the priority of the suggestion by consolidating customer impact under one feedback. The product team would provide the updates if they view it. Thank you for helping us build a better Azure DevOps!
Here is a ticket with similar issue.
In Classic UI Release pipelines, you can specifiy pre-stage and post-stage Gates.
However using YAML releases, and projects Environments, you can only use the Approval & Checks feature on the Environment.
AFAIK this only behaves as an pre-deployment gate. Is there a way to perform a post-deployment check using YAML releases?
Sorry, it's not available right now. But there is a related feature request in our user voice site:
Add pre and post-deployment approvals for multi-stage pipelines (YAML), similar to release definitions
https://developercommunity.visualstudio.com/idea/567845/add-pre-and-post-deployment-approvals-for-multi-st.html
Kindly vote up and track the status on it. Our PM will also review it.
A few years ago, our team made the full transition to Azure DevOps. Before that, we had a mixture of on-prem TFS and Subversion but went to the Azure DevOps as it was easier to maintain project status between our developer and BA teams. At that time, for each project the team was working on, we just created a new "project" in Azure DevOps, but over the course of the past few years, we have found that using that method doesn't lend itself to helping us track metrics across all of those projects. We also see that maintaining multiple, separate backlogs is not ideal as we have developers spread across multiple sprints at the same time in different projects without a single place for the team leads or scrum master to fully know what their team members are working on in a single day.
Now, we've made use of queries, but those only go so far, so we've made the decision to merge our projects into a single "project". My scrum master and I have been looking at Naked Agility's merge tool, as outlined in this link: https://blog.devopsabcs.com/index.php/2019/06/12/one-project-to-rule-them-all/.
Has anyone used this tool and how well did it work for you? Also, are there any other options for merging projects together as this tool seems really complex (which the developer states is the case).
Azure DevOps: Merging two projects together
Sorry for any inconvenience.
I am afraid merging projects into a project is currently not supported in azure devops.
There is a Under Review user voice about make it possible to move a Team Project between Team Project Collections.
Merging two projects is not a simple task, it contains not only source code, build/release history, workitems and other watch outs were mainly around access and security:
External API integrations such as Web Apps, Function Apps, JIRA, Service Now
External inbound app authorisations
External outbound app authorisations such as Azure Service Principals
Variable Group authorisations to YAML Build Pipelines
Library reference updates including KeyVault
etc
This refactoring ended up being much more work than the code merge itself.
Besides, there is a Azure devops extension Migration Tools for Azure DevOps, which allow you to migrate Teams, Work Items, and Plans & Suits from one Project to another in Azure DevOps/TFS both within the same Organisation, and between Organisations. Watch the Video Overview to get you started in 30 minutes. This tool is complicated and its not always easy to discover what you need to do.
Hope this helps.