Michael Christensen

My feedback

  1. 638 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Christensen commented  · 

    If you have a setup with a lot of variables targeting different steps/roles/environments, it becomes difficult to predict what the exact variable values delivered to each step will be.
    For instance, I might have forgotten to define an important variable scoped for our production environment. My deployment script will then fail because the value is missing.
    It would cut down on the deployment error rate if it was possible to ask a release to show the variables that would be available in each of the steps associated with it, given an environment.

    A nice to have would be to be able to compare which variables are available to the same step in the different environments side-by-side, to spot variables available to only a subset of the environments

    Michael Christensen supported this idea  · 
  2. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Christensen shared this idea  · 

Feedback and Knowledge Base