Azure-devops-docs: where is yaml syntax?

[katlimruiz]

where is yaml syntax?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e1c633b9-c8b2-e05d-de2c-7754894d28fd
• Version Independent ID: df031b76-0fe7-e138-dd36-2736757a97fd
• Content: Manual Intervention task - Azure Pipelines
• Content Source: docs/pipelines/tasks/utility/manual-intervention.md
• Product: devops
• Technology: devops-cicd
• GitHub Login: @RoopeshNair
• Microsoft Alias: ronai

[RoopeshNair]

Manual Intervention is not supported in YAML pipeline. We haven't closed on the design, unfortunately no time-line that can be shared at this point in time. We will continue to track it

[rjminchuk]

It's been a few months, so I was wondering if there are details that can be shared about this now. Is there a time-line for this yet? There are seemingly no stage Gates/Approvals or Manual Interventions tasks for yaml release pipelines at the time of this writing.

[katlimruiz]

Good news, it is there and . I am using it already.
On Sep 18, 2019, 17:06 -0500, Rich Minchuk [e-mail], wrote:

It's been a few months, so I was wondering if there are details that can be shared about this now. Is there a time-line for this yet? There are seemingly no stage Gates/Approvals or Manual Interventions tasks for yaml release pipelines at the time of this writing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[rjminchuk]

Would you share your YAML? I'm trying this in a yaml pipeline (not a classic Release pipeline), but it's not working..

...
- stage: 'Gate_for_QA'
  dependsOn: 'Deploy_to_Dev'
  jobs:
  - job:
    pool: 'server'
    steps:
    - task: ManualIntervention@8
      displayName: 'Baseline Smoke Test in QA'
      inputs:
        instructions: 'my instructions.'
        emailRecipients: '["84cdwfd..........d385014314"]'
- stage: 'Deploy_to_QA'
  dependsOn: 'Gate_for_QA'
  jobs:
  - job:
    pool: 'my_agent_pool'
    steps: 
    - bash: echo 'deploy to qa1'

I copied the ManualIntervention@8 tasks yaml out of a classic release pipeline and set it to run on the "server," but I receive the following error message:

Gate_for_qa:Job: "Task execution section of task definition for ID: bcb64569-d51a-4af0-9c01-ea5d05b3b622 is either missing or not valid."

I also tried the task from an agent running in my own agent pool, but received a different error.

[RoopeshNair]

As I mentioned earlier, Manual Intervention is not supported in YAML pipelines yet. We have it on our backlog. tentatively 4-5 months based on current priorities. We are working on issues that impact broader set of users. We will continue to monitor this.

[katlimruiz]

You need to do the following:

1. Configure an new Environment e.g. Staging (in Pipelines/Environments)
2. On the right side, click on menu, click on Checks, add one and assign specific users or groups that can approve this.
3. Your Yaml should be something like this:

- stage: 'Deploy_to_QA'
  jobs:
  - deployment: Deploy_to_QA
    pool: 'my_agent_pool'
    environment: Staging <<<<<< This is the key
    strategy:
      runOnce:
        deploy:
          steps:
          - bash: echo 'deploy to qa1'

Add the environment entity below the job (which I defined as deployment, not a regular job).

NOTE: The only downside which I already reported to MS is that when the pipeline is waiting for the check it shows In Progress so it is confusing (you will see many pipelines "running", though they are not).
Besides that it works very well.

At first it drove me off the button Add Resources, and the only thing available now is Kubernetes, so I thought it was incomplete. But then I realized that it didn't require any. The key was the Checks option that was added some months ago.

So actually this is moving out of the "Manual Intervention" thread, and should move to a "Multistage pipelines" thread. Since Manual Intervention seems to never migrate to Yaml which is fine.

[rjminchuk]

It looks like I was just flat out wrong in my earlier post. It does appear that approvals (known as checks in the environments sub page of the pipeline tab) are a feature in yaml pipelines. I had previously equated Environments with Deployment Group Agents, where an environment might be a machine with an agent installed on it, and I ignored it as a tool to facilitate approvals.

Thank you @katlimruiz. You put me on the right path!

Thank you @RoopeshNair, I was really looking for approvals (checks), and Katlim's answer pointed me in the right direction.

[RoopeshNair]

@rjminchuk - thanks for confirming, yes we do support approvals on environments, soon you will be able to set them on other resources like Service connections etc.

[anderseide]

Anything new on when this is available and supported for other services than k8s?

[RoopeshNair]

Environments will start supporting VM resources soon. The work is near complete. We will start rolling out in 3-4 weeks time. You will be able to add the VMs to an environment an use it in YAML pipeline with rolling deployment strategy.

[anderseide]

How about other services? The feature we're looking for more specifically is primarily the Approval workflow that Environments support.

Probably not the right thread, but I would love to see that as a dedicated Task. That way it could be used anywhere in the pipeline, and could easily be added as a dependency for another Job/Stage

[RoopeshNair]

Once VM support is rolled out, we will pick-up other Azure resources.

The feature we're looking for more specifically is primarily the Approval workflow that Environments support.

Approvals are available on environments and support for approvals on service connections and agent pools is getting rolled out. Manual validation as a step in the workflow is on our backlog. However, it might be a while before we can get to it. (4-5 months)

[djpugh]

If this is the case, then the azure devops pipeline assistant should probably not show this in a non-release pipeline - it currently provides it as a configuration in yaml option that you can add, which is definitely at odds with these comments...

[benallpass]

@RoopeshNair Do you have any updates on when this might be available?

[RoopeshNair]

@raiyanalam for Manual validation step in YAML

[rjminchuk]

Approvals are available on environments and support for approvals on service connections and agent pools is getting rolled out.

@RoopeshNair and @raiyanalam, do either of you have an ETA on GA (or preview) of these features?

[RoopeshNair]

@rjminchuk - manual validation step is scheduled for next quarter. Approvals are avaiable: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/approvals?view=azure-devops&tabs=check-pass

[rjminchuk]

@RoopeshNair, Thank you. I am currently using environment approvals. 👍

I'm specifically requesting information on service connection and agent pool approvals which you mentioned previously. Do you have an ETA on GA/preview on agent pool approvals?

Approvals are available on environments and support for approvals on service connections and agent pools is getting rolled out.

[RoopeshNair]

It should be available on service connections and agent pools. Let me know if you can't access. I just got this from the doc link..

[rjminchuk]

Awesome! Thanks @RoopeshNair !

[rjminchuk]

I was able to find agent pool approvals in Azure DevOps, but missed it in the documentation.