![]() In the following example, the deployment was approved and the approval status is displayed on the card. ![]() Approvers can review the details of the request in the notification and take appropriate action. Whenever the running of a stage is pending for approval, a notification card with options to approve or reject the request is posted in the channel. Both of these subscriptions are created by default when you subscribe to the pipeline. You can approve deployments from within your channel without navigating to the Azure Pipelines portal by subscribing to the Release deployment approval pending notification for classic Releases or the Run stage waiting for approval notification for YAML pipelines. For YAML pipelines, subscriptions are created for the Run stage state changed and Run stage waiting for approval notifications. The channel will start receiving Release deployment started, Release deployment completed and Release deployment approval pending notifications. For Build pipelines, the channel is subscribed to Build completed notification. The subscribe command gets you started with a few subscriptions by default. The pipeline URL can be to any page within your pipeline that has definitionId or buildId/releaseId in the URL. You can also monitor a specific pipeline using the following command: /azpipelines subscribe ![]() The project URL can be to any page within your project (except URLs to pipelines). To start monitoring all pipelines in a project, use the following slash command inside a channel: /azpipelines subscribe ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |