Skip to content

Settings and activity

3 results found

  1. 35 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

    5 comments  ·  Product Feedback » Administration  ·  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)
    Ben Byers supported this idea  · 
  2. 166 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

    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)
    Ben Byers supported this idea  · 
    An error occurred while saving the comment
    Ben Byers commented  · 

    Just to elaborate on this a bit: I'd like to have an added option, something like: "Pre-Release Task or Approval", to the Manual Intervention steps (and email or see my other idea about adding notification to MI steps: https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6297235).

    For immediate deployments this would have very little impact, but for scheduled releases, when the step gets processed it will run immediately (subject to run order of course!). Doing so would allow you to have a multiple approval steps that run as soon as the release is promoted, but then the actual release steps would hold off till the scheduled time. Some manual intervention steps should only run at deployment so I wouldn't want to make this universal, but configurable for each step.

    The scenario I'm look at is to have 3 manual intervention steps for a release.
    Step 1: Approval from immediate manager (pre-release)
    Step 2: Approval from Stake Holder (pre-release)
    Step 3: Engineering ready (at release time)
    Step 4-X : Code deploy.

    Steps 1 & 2 need to happen during regular business hours, but step 3 should only happen at the time the deployment is scheduled. It's there to ensure that engineering is on site and everyone's ready to supervise the release.

  3. 37 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

    3 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)
    Ben Byers supported this idea  · 
    Ben Byers shared this idea  ·