I suggest you...

When deploying project containing Deploy Release step, allow previewing steps and excluding machines from child deployments

Currently when deploying a project containing one or more Deploy Release steps (https://octopus.com/docs/deployment-process/coordinating-multiple-projects/deploy-release-step), there is no ability to preview the deployment steps that will be executed in the child deployment, nor the ability to exclude machines from the child deployment.

It would be nice to surface this information on the create-deployment page of the parent project.

34 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
AdminOctopus Developer (Software Engineer, Octopus Deploy) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Hugo commented  ·   ·  Flag as inappropriate

    For our company will be a great functionality because our project are deployed in several target in the same environments.

  • Ulf Axelsson commented  ·   ·  Flag as inappropriate

    Yes please!

    In our case we would like to be able to disable Manual Intervention steps in the child deployments so that we can schedule the master deployment without it stopping during the scheduled execution.

    Since the intent is to be able to do individual deployments (for patching or other minor fixes) we still want to keep those steps in the individual deployments but also make it easy to make major release deployments.

  • tfbryan commented  ·   ·  Flag as inappropriate

    Being able to programmatically tell the Parent deployment which target machine it should deploy to would be huge. For instance, we need to deploy several packages and orchestrate them within a rolling deployment. Currently, I don't see that there is any way to do that with Release A Deploy steps.

Feedback and Knowledge Base