-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[enhancement]: Allow ManualValidation task to limit who can approve the step #18385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yes, this feature would be great. |
second that, you should also not be able to approve your own pipeline runs. right groups should be added to the environments as it's already there and can be re-used in the manual validation process. |
Any movement on this? Seems like the only logical way to have an approval process in CI, rather than anyone being able to approve/deploy |
Queue Build is allowed to Contributor. And you need to be a contributor to Build pipelines. So evryone can resume the task. |
It seems |
@VictorIreri Thank you, I did know there was a new version. The new parameter approvers works just fine |
@stetou The warning is no longer present in the docs but having tested it, I can't seem to get it to work as expected for a single user or a team. 🤔 |
It doesn't matter where I click on the View button - the result is the same. |
I apologize for the misinformation. The task is working correctly. The issue was with usernames. Azure DevOps usernames are case-sensitive, so [email protected] != [email protected]. |
I had a typo in my configuration which I've fixed and now I see exactly what you posted @stetou. Thanks. 👍 |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Task name
ManualValidation
Describe your feature request here
Whilst environments allow us to have validation on a whole pipeline stage, sometimes its ideal to have approvals on just a single job within a stage and the ManualValidation task is ideal for this
However ManualValidation currently allows anyone with Queue Build permissions to approve the validation. It would be nice to limit who can approve the task to people specified in the task inputs
The text was updated successfully, but these errors were encountered: