My feedback

1. Allow approval step for scheduled deployment happen before actual deployment

   385 votes

   Vote Vote Vote

   Vote

   Sign in

   prestine

   Your name

   Your email address

   (thinking…)

   

   Password

   Sign in with: Facebook Google

   Forgot password?

   Create a password

   I agree to the terms of service

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   12 comments  ·  General  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   An error occurred while saving the comment
   Job Vermeulen commented  ·  December 03, 2014  ·  Edit…  ·  Delete…

   Exactly the problem i'm facing.

   Save Submitting...
   Job Vermeulen supported this idea  ·  December 03, 2014

2. 'Dry Run' Deployment

   638 votes

   Vote Vote Vote

   Vote

   Sign in

   prestine

   Your name

   Your email address

   (thinking…)

   

   Password

   Sign in with: Facebook Google

   Forgot password?

   Create a password

   I agree to the terms of service

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   23 comments  ·  General  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   started  ·  AdminOctopus Developer (Software Engineer, Octopus Deploy) responded

   Work has begin on providing a tool to evaluate variables before deployment
   https://github.com/OctopusDeploy/Issues/issues/4221

   At the moment we don’t have further plans to apply config transforms before a release but this should help solve the bigger question of “what will my all my variable values actually be at run time”

   Job Vermeulen supported this idea  ·  December 03, 2014