I have projects in different AzureDevops instances created at different times.
In my current project the build pipeline has the New Yaml Pipeline Experience. My old projects have the old visual creation experience. Is it possible to toggle between the two views?
If so how do I go from the New YAML pipeline to the old view?
This enable a preview link looks promising but the NEW YAML pipeline creation is no longer a toggle option for me
You can still create pipelines with the visual editor with the new YAML Pipeline features turned on. Its easy to miss the option though. Just create a new pipeline and then at the bottom of the page click the link for the classic editor.
Is it possible to toggle between the two views?
If what you want is convert the current pipeline which is using YAML to view as Classic editor, sorry to say, no, we did not support this toggle between YAML and Classic Editor until now.
Now, we only support toggle the pipeline that code with Classic editor to YAML by using the "View YAML" button. But the reverse is not possible.
But I thinnk it would be a good feature that make configure in pipeline more convenient. Users can free to toggle between YAML and Classic Editor. You can raise this feature suggestion to our official Suggestion Feature forum, our Product Group and PMs will reviewing these ticket regularly, and consider to take it as our Roadmap.
Related
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 evaluating Azure Boards / Azure DevOps and I wish to restrict what a Stakeholder (in this case, a customer) can see and do.
I have managed to limit what a Stakeholder can do, but is it possible to completely hide the Pipelines, Artifacts and Project Settings panes from Stakeholder?
Se the image. I want to completely hide the panes marked in red.
Image of panes to be hidden
I am not sure if we can show/hide the DevOps Services in top-level, based on a specific role. This is only available for the project level.
https://dailydotnettips.com/turning-azure-devops-service-on-or-off/
and these settings can only be controlled by the Project / Org administrator.
We cannot get rid of the Pipelines from the view for the stakeholders. Yes, we can turn off the pipelines service from the project settings overview page, thus the pipelines node will disappear from the view. However it's applied to entire project, that means all other users also cannot see the pipelines.
As a workaround you can manage security for all pipelines and Artifacts for each project, just deny all of the related permissions for the stakeholder.
In addition, I found a related suggestion ticket, you can follow and vote this ticket to get the latest news.
Currently I'm developing a custom plugin to Azure devops, and met with an issue when I set a scan in the build pipeline, after scan completed, I was not able to see the custom summary tab, in the Azure devops 'Summary' tab section.As the root cause for this, What I found was , I have accidentally switched-on the below features in the Azure devops preview features section.
Experimental Themes
Multi-stage Pipelines
Further, I was able to see the custom 'summary' section after scan completes, when the above mentioned features are in switched-off mode.
In the development, custom summary section is placed in the,below mentioned placeholder,
".build-info-tab",
"ms.vss-build-web.build-results-summary-tab"
So, When those preview features in switched-on mode, the placeholder which we are placing the custom summary section, is different than the above mentioned placeholder? If not, how can I implement my custom summary section into, Azure devops summary section when the experimental and multi-stage preview features are in switched-on mode ?
Any suggestion or advice will be highly appreciated. Thanks in advance!
I can reproduce your scenario. I have to place my custom section to the build results view as results tab to display it as workaround. Below is the targets:
"id": "build-custom-tab",
"type": "ms.vss-build-web.build-results-tab",
"description": "A tab contributing to build results view",
"targets": [
"ms.vss-build-web.build-results-view"
]
You can also report this issue to Microsoft Dev team, Hope they could look into this issue.
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.
I am working on a requirement where I have to generate the load test report using artillery tool and publish the report stats into our Azure DevOps pipeline.
Artillery generates the report into html format and same I want to show into Azure DevOps pipeline. How can i do it?
I know Azure pipeline supports only Junit reports but still is there a way I can publish the artillery HTML report?
If without any plugin or extension support, until now, the HTML report would not be compiled successfully, then map corresponding attributes into pipeline directly. As you know, until now, it only support the format: TRX, JUnit, NUnit2, NUnit3, xUnit2, CTest.
As work around, you can define your customized extension. With this extension, add one new section into pipeline first, use task to publish this HTML report into this new section, then map and display its attributes into this section.
There has a sample extension can for you refer to: vsts-publish-html-artifact.
Note:
Since this extension programmed 4 years ago and no longer maintained now, also most of our official doc content has been updated with the latest grammar, such as categories and etc. I modify johnwalley's script, thus you can directly use it now. Due to my github repository: Merlin-Extension.
You can also extend the functionality of this extension by adding scripts based on your individual needs. Refer to this doc for extension script written: https://learn.microsoft.com/en-us/azure/devops/extend/get-started/node?view=azure-devops
The work around I provide above can only consider as a temporarily method. Since Xml reports are too basic and html is more useful in many cases/ tools, I also looking forward to the feature for HTML report Published in pipeline can be expanded into Azure Devops.
Here has a feature suggestion ticket exists on our official forum. We can vote and comment it there to make it has a broad community impact, also will improve the Azure Devops experience. Thus our product group will consider to take this feature into our develop roadmap.