OctopusDeploy / OctoTFS

| Public | Octopus extensions for Azure DevOps, TFS, VSTS, and VSO
https://marketplace.visualstudio.com/items?itemName=octopusdeploy.octopus-deploy-build-release-tasks
Other
0 stars 41 forks source link

feat: await task #282

Closed benPearce1 closed 1 year ago

benPearce1 commented 1 year ago

depends on https://github.com/OctopusDeploy/api-client.ts/pull/142

TODO: needs a new step icon

image

- task: OctopusDeployReleaseTenanted@6
  name: 'releaseTenants'
  inputs:
    OctoConnectedServiceName: 'octo'
    Space: 'Default'
    Project: 'New Awesome Project'
    ReleaseNumber: '0.0.3'
    Environment: 'test'
    DeployForTenants: |
      tenant 1
      tenant 2
      tenant 4
- task: OctopusAwaitTask@6
  inputs:
    OctoConnectedServiceName: 'octo'
    Space: 'Default'
    Step: releaseTenants
    PollingInterval: 5
    TimeoutAfter: 60

PollingInterval and TimeoutAfter are optional, default to 10 seconds and 600 seconds respectively

Result:

Starting: OctopusAwaitTask
==============================================================================
Task         : Await Octopus Task Completion
Description  : Await the completion of a execution task
Version      : 6.0.31
Author       : Octopus Deploy
Help         : Version: 1.0.31. [More Information](https://g.octopushq.com/TFS-VSTS)
==============================================================================
Deployment to environment 'dev 2' is 'Executing'
Deployment to environment 'dev' is 'Executing'
Deployment to environment 'dev 2' is 'Executing'
Deployment to environment 'dev' is 'Executing'
Deployment to environment 'dev 2' is 'Executing'
Deployment to environment 'dev' is 'Executing'
Deployment to environment 'dev 2' is 'Executing'
Deployment to environment 'dev' completed successfully
Deployment to environment 'dev 2' is 'Executing'
Deployment to environment 'dev 2' completed successfully
Finishing: OctopusAwaitTask

In UI (CI) mode the user needs to set the output variable reference, then use that reference as the Step source. This is because all output variables are scoped, but the UI mode doesn't have a step Id.

image

image