azdev-release-orchestrator
azdev-release-orchestrator copied to clipboard
Azure DevOps extension to manage and orchestrate release pipelines
The fact that the Orchestrator step holds an agent hostage while waiting for the child task to complete creates some issues, especially when using them for parallel deployment of many...
Hi, testing the plugin, I didn't find a way to fill the _Comment (optional)_ field into _Waiting for review_ form.  Looking into your code, seem you support the field...
Hi, I don't see an option to set a variable scope when defining variables for a release pipeline. From previous experience with the API, it assumes variable scope is "Release",...
Would it be possible to mark the task as skipped if no release is found that matches the search criteria? We have a micro-service architecture and not every service has...
Hi! Truly a gem of a task for people who need to orchestrate a lot of pipelines! Any suggestion how to handle stage names with commas and spaces in the...
I called different stages in a multistage environment and it didn't work. So, I set the debug flag and the function "getStages" respone a list of displayNames instead of stage...
Can we integrate yaml pipeline and classic pipeline through Release Orchestrator pipeline? For example - I have to run a sequence of pipelines where i have to run few classic...
The error we are seeing when we attempt to upload the extension to Azure DevOps Server, is "Extension validation error Task definition input 'strategy' and Task definition input 'proceedSkippedStages' must...
Rather than specifying a filter to define what artifacts to use when running a new release, it would be helpful to specify the artifacts to use directly in the release...
could you add a new strategy that is just approval? This would be very useful because when you have microservices and releases are generated, not always to deploy all the...