My feedback

1. '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”

   Tim Thompson supported this idea  ·  October 16, 2016
   An error occurred while saving the comment
   Tim Thompson commented  ·  October 16, 2016  ·  Edit…  ·  Delete…

   We have a large percentage of 'first' deploys to an environment fail purely due to the mental tax of trying to project the current variable configuration into it's final deployed state. An ability to 'dry run' and eyeball the resulting config files would almost entirely eliminate the need for our current practice of deploying to an environment _before_ it's required simply to confirm config values are correct.

   Save Submitting...