← Help shape the future of Octopus Deploy

Settings and activity

  1. Allow approval step for scheduled deployment happen before actual deployment

    166 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  ·  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)
    Close
    Close
    An error occurred while saving the comment
    Dean Meehan commented  · 

    We need our QA team to sign off a release before the dev team can deploy the applications to production. Our current process is:
    1. TeamCity builds/tests and (if all's good) creates the NuGet package
    2. Deploy to Dev Environment is started automatically
    3. The Dev team (Group) can Deploy to UAT
    4. The QA team can then approve this UAT Release
    5. The Dev Team (Group) can now deploy to prod (As UAT has been approved)

    Currently, this can be done by using Manual Intervention, but this isn't the correct way to do it. There should be a step between each Environment

    Dean Meehan supported this idea  · 

  2. Providing Octopus Server Proxy Whitelist

    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  ·  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)
    Close
    Close
    Dean Meehan shared this idea  ·