Skip to content
← Navigate to roadmap.octopus.com

Settings and activity

5 results found

  1. Expand Variable Conditionals to include OR/AND statements

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Product Feedback » Integration  ·  Admin →
    Emil shared this idea  · 

  2. Add cmdlet to download artifact

    20 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Product Feedback » Deployments  ·  Admin →
    An error occurred while saving the comment
    Emil commented  · 

    I need to examine the content of the artifact, however calling the API after creation even with a delay does not seem to work so having a cmdlet will be great!

  3. Allow configuration transforms for JSON files

    16 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Product Feedback » Deployments  ·  Admin →
    Emil supported this idea  · 

  4. Audit on step template

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Product Feedback » Installation  ·  Admin →
    Emil supported this idea  · 

  5. Support Required Variables

    6 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Product Feedback » Deployments  ·  Admin →
    Emil supported this idea  · 
    An error occurred while saving the comment
    Emil commented  · 

    I guess this could be extended to something like "Variable Policy" for example:
    - all variables available in one environment must be identical in this environment
    - use all variables from another environment i.e. if a variable is not available in current environment try to resolve it from another environment

    The use case here is to apply "Variable Policy" rules in Pre-Prod & PROD environments to stop false "green" releases with missing or incorrect variable values. For example we can fully test releases in Pre-Prod but cannot test in PROD and the variables setup is manual step with high risk!

    I guess the current implementation of DryRun will solve the problem of what happens of variables for a particular target environment :)
    https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6169634--dry-run-deployment