Thanks! Not exactly that approval process, but you can integrate Pipelines and Teams, for approval, as described here: learn.microsoft.com/en-us/azure/devops/pipelines/integrations/microsoft-teams?view=azure-devops
Thanks! There is no much else to say about this manual validation task, but I have other videos (especially the one about Azure DevOps environments) that talk about approvals more in general. What would you like to see about this?
Hi, is it possible to change the text of the reject an approve Button ? Also is it possible to change the Green Hook to a red cross or other way round ? Thanks for the nice vid.
@CoderDave, I've a question. If i have a parameter that is passed into the .yml file that is an object with many email addresses how can i add these to the "notifyUsers" section?
Uhm, I haven't tried if this works, but in theory you could pass a stringified JSON array (containing the emails) and them deserialize it and feed it to the notifyUsers. The only thing I am unsure is that... I think the field is read at "compile time" for the pipeline. If that is the case, it wouldn't work because the emails from your object are applied at runtime.
I actually have a couple of deployment stages pertaining to 3 different Environments. I want to add this approval gate in my last (Prod) environment. I'm confused as to how to add it because, here there is a complete job that needs to be implemented. So If I implement it this job and then a deployment with the PROD environment, if the approval is rejected, will the deployment still be triggered (which is actually not desired otherwise there is no point of implementing an approval gate) ?
if you add an approval to the environment directly, then the deployment to that specific environment will not happen if you reject it, but will still be done for the other environments. If instead you use manual validation task, explained in this video, and you reject it in job 2, then jobs 3 and 4 will not happen (assuming that job 3 depends on job 2)
Hey, nice video, always learning something new from you. I got a question, what would be the difference between deployment approvals vs this manual validation? setting up the environments would not be necessary I guess, over than that I thkn they are quite equal, don't they? Thanks!
Thanks for the compliment and always happy to help and share ☺️to your question: deployment approvals in YAML are pre-deployment, meaning that it’s a “confirmation” that the deployment can start. And there is no “post-deployment “ approvals in YAML like there are in the classic pipelines. The manual validation instead can be placed anywhere in a stage… and doesn’t need to be related to a deployment or an environment. So I’d say they are more flexible, but at the same time they are less integrated
Yes you can use it for any kind of stage in the YAML pipeline. Wether it’s a build stage or a deployment stage, this will work as long Asia runs in an agentless job
Great question. I had to look it up because my understanding was that it should be supported. However, unfortunately, it is not supported in the on-prem products (developercommunity.visualstudio.com/t/Manual-Validation-task-not-available-in/1340627?space=22&q=Manual+Validation)
@CoderDave - I have created yaml pipeline for infra creation using Terraform tasks. As you said manual validation will work only with agentless jobs. In that case how can i integrate this manual validation which has terraform tasks>
Hey! What if I have a job with multiple tasks and I need to put manual validation in between these tasks. So, I need this manual validation to be a task, not a job. I know that it is not possible but is there any alternative?
Unfortunately I don’t think there is any way to achieve that, because even if you implement a script that just waits for something… every task has an execution timeout which will expire if you don’t act quick enough 🙁
Hi, great content as usual. Can this type of validation be integrated with microsoft teams as appovals?
Thanks! Not exactly that approval process, but you can integrate Pipelines and Teams, for approval, as described here:
learn.microsoft.com/en-us/azure/devops/pipelines/integrations/microsoft-teams?view=azure-devops
Good intro! Do you have any plans on expanding the topic of approvals in another video?
Thanks! There is no much else to say about this manual validation task, but I have other videos (especially the one about Azure DevOps environments) that talk about approvals more in general. What would you like to see about this?
Hi, is it possible to change the text of the reject an approve Button ? Also is it possible to change the Green Hook to a red cross or other way round ? Thanks for the nice vid.
Not that I know of, unfortunately
@CoderDave, I've a question. If i have a parameter that is passed into the .yml file that is an object with many email addresses how can i add these to the "notifyUsers" section?
Uhm, I haven't tried if this works, but in theory you could pass a stringified JSON array (containing the emails) and them deserialize it and feed it to the notifyUsers.
The only thing I am unsure is that... I think the field is read at "compile time" for the pipeline. If that is the case, it wouldn't work because the emails from your object are applied at runtime.
I actually have a couple of deployment stages pertaining to 3 different Environments. I want to add this approval gate in my last (Prod) environment. I'm confused as to how to add it because, here there is a complete job that needs to be implemented. So If I implement it this job and then a deployment with the PROD environment, if the approval is rejected, will the deployment still be triggered (which is actually not desired otherwise there is no point of implementing an approval gate) ?
if you add an approval to the environment directly, then the deployment to that specific environment will not happen if you reject it, but will still be done for the other environments.
If instead you use manual validation task, explained in this video, and you reject it in job 2, then jobs 3 and 4 will not happen (assuming that job 3 depends on job 2)
Hey, nice video, always learning something new from you.
I got a question, what would be the difference between deployment approvals vs this manual validation? setting up the environments would not be necessary I guess, over than that I thkn they are quite equal, don't they? Thanks!
Thanks for the compliment and always happy to help and share ☺️to your question: deployment approvals in YAML are pre-deployment, meaning that it’s a “confirmation” that the deployment can start. And there is no “post-deployment “ approvals in YAML like there are in the classic pipelines. The manual validation instead can be placed anywhere in a stage… and doesn’t need to be related to a deployment or an environment. So I’d say they are more flexible, but at the same time they are less integrated
@@CoderDave so can I use this manual validation approval yaml configuration in deployment pipeline ?
Yes you can use it for any kind of stage in the YAML pipeline. Wether it’s a build stage or a deployment stage, this will work as long Asia runs in an agentless job
@@CoderDave Thanks much 👍 I am excited to try in my home lab. Thank you again for sharing information ☺️
Is this available in on-prem Azure Devops Server?
We are running Azure Devops Server 2020 and I can't find this task anywhere.
Great question. I had to look it up because my understanding was that it should be supported. However, unfortunately, it is not supported in the on-prem products (developercommunity.visualstudio.com/t/Manual-Validation-task-not-available-in/1340627?space=22&q=Manual+Validation)
@CoderDave - I have created yaml pipeline for infra creation using Terraform tasks. As you said manual validation will work only with agentless jobs. In that case how can i integrate this manual validation which has terraform tasks>
You’d need to do your terraform stuff in a “a normal” agent job… then add an agent less job after it to have the manual validation.
Hey! What if I have a job with multiple tasks and I need to put manual validation in between these tasks. So, I need this manual validation to be a task, not a job. I know that it is not possible but is there any alternative?
Unfortunately I don’t think there is any way to achieve that, because even if you implement a script that just waits for something… every task has an execution timeout which will expire if you don’t act quick enough 🙁
@@CoderDave Yes, totally agree. Thank you for your quick response!
Is there a way for me to prompt user inputs in that task just like 'Instructions' for variables?
Can we add hyperlink in the instruction?
Just checked. Currently everything is treated as plain text :(
Can we populate variable value in instruction string ?@@CoderDave
Still in preview 2 years after ahah