Skip to content
← Please visit roadmap.octopus.com

Settings and activity

4 results found

  1. Add the ability to skip steps based of the value of a prior steps output variable.

    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

    2 comments  ·  Product Feedback » Deployments  ·  Admin →
    An error occurred while saving the comment
    Michael Noonan commented  · 

    Oh, and this blog post goes into more detail: https://octopus.com/blog/deployment-process-uservoice-update#allow-the-run-condition-of-a-step-to-be-based-on-a-variable

    An error occurred while saving the comment
    Michael Noonan commented  · 

    Does this look like it fits the bill for you? https://github.com/OctopusDeploy/Issues/issues/2984 This shipped in Octopus 3.7.13

  2. Automatic release creation to multiple channels

    112 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

    13 comments  ·  Product Feedback » Releases  ·  Admin →
    An error occurred while saving the comment
    Michael Noonan commented  · 

    Hi All,

    My general recommendation is to use one of the CI extensions for TeamCity, TFS, VSTS or Jenkins etc, or `octo.exe create-release` (which is what these all call under the hood). These tools will automatically detect the best channel to use when creating a release which means you shouldn't need to leak channel details into your CI tooling.

    https://github.com/OctopusDeploy/Issues/issues/2494

  3. HA Active Task Handoff Between Nodes (for Drain)

    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

    1 comment  ·  Product Feedback » Installation  ·  Admin →
    An error occurred while saving the comment
    Michael Noonan commented  · 

    Hi Jai, that's an interesting thought. Maybe we could signal that a task should "pause" - very similar to a manual intervention or guided failure does today - to be picked up by another node.

    One thing you can do in the meantime is to dedicate some nodes in your cluster handling HTTP requests only, by setting their task cap to 0, and some to running tasks by setting the task cap > 0. You could then direct HTTP requests to the API nodes, and let the task running nodes do all the background work.

    We are also working on some ideas to make the "dozens of teams with 100s of projects" easier to scale and manage - watch our blog for more details.

  4. Support multiple SSL bindings to Octopus Server using SNI

    9 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 » Installation  ·  Admin →
    Michael Noonan shared this idea  ·