Skip to content
← Please visit roadmap.octopus.com

Settings and activity

6 results found

  1. Allow variables to be used for Channel Version Rules

    1 vote

    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 →
    tfbryan 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 →
    tfbryan supported this idea  · 

  3. Support creation of releases in child projects during "Deploy a Release" step

    8 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 » Deployments  ·  Admin →
    An error occurred while saving the comment
    tfbryan commented  · 

    Here's what I did >>> In the child projects, set up a trigger to auto-release. Then when you go to create a release from the project that contains the "Deploy a Release" step, it will have all the latest releases available.

  4. Automatic variable inclusion

    4 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  ·  Admin →
    tfbryan shared this idea  · 

  5. Store sensitive variable values in Azure Key Vault

    148 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

    Under Consideration  ·  16 comments  ·  Product Feedback » Integration  ·  Admin →
    tfbryan supported this idea  · 

  6. When deploying project containing Deploy Release step, allow previewing steps and excluding machines from child deployments

    18 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
    tfbryan commented  · 

    Being able to programmatically tell the Parent deployment which target machine it should deploy to would be huge. For instance, we need to deploy several packages and orchestrate them within a rolling deployment. Currently, I don't see that there is any way to do that with Release A Deploy steps.

    tfbryan supported this idea  ·