Skip to content

Settings and activity

4 results found

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Product Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stephen Schaff shared this idea  · 
  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stephen Schaff shared this idea  · 
  3. 43 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Product Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stephen Schaff commented  · 

    Just thought I would post the ugly that this causes. My steps have to have this as the "Notes":
    ---------

    DO NOT CHANGE THE STEP NAME!

    If you must, then you need to update the Helm Chart, the Team City scripts and the embedded PowerShell scripts for this step to use the new step name in the variable references.
    ---------

    At the very least, the Octopus UI should warn the user that changing the name may break scripts that reference variables created in that step. Maybe only show it if there are scripts enabled for the step at at least one of them contains the text "Set-OctopusVariable" (or equivalent for other languages).

    An error occurred while saving the comment
    Stephen Schaff commented  · 

    This is a big issue when building templates for other users. They don't know that they can't just change the name of the step to fit what they are doing.

    I don't understand why I can't just add a project level variable. None of this "Octopus.Action[StepOne].Output.TestResult" business. When I call Set-OctopusVariable -name "TestResult" -value "Passed" then I should be able to get at that with #{TestResult}

    If it conflicts with an existing project level variable, then throw an error and fail the deployment (or just overwrite the value.)

    That way if I want my Output variable to be step step specific, I can add it to the name of the variable I am creating. For example #{StepOneTestResult}

    Stephen Schaff supported this idea  · 
  4. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stephen Schaff shared this idea  ·