Wenzel, Toni

My feedback

  1. 169 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General » Integration  ·  Flag idea as inappropriate…  ·  Admin →
    Wenzel, Toni supported this idea  · 
  2. 192 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Wenzel, Toni supported this idea  · 
  3. 106 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Wenzel, Toni supported this idea  · 
  4. 98 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Wenzel, Toni commented  · 

    My scenario:
    1.- 200+ Octopus projects
    2.- Each of those projects has a update DB step configured to run on "database-updater" target role.
    3.- Production environment has 5 targets with the "database-updater" role.

    My requirements:
    1.- For each project, the updated DB step needs to run once on one target only.
    2.- When many projects are deploying at the same time, I want the work to be distributed among the 5 targets (so if I deploy 100 projects at the same time, each "database-updater" target would run 20 projects' update DB step).

    At the moment this is only possibly by creating multiple roles "database-updater1" etc and assign those roles fix to the projects.

    Please provide an option to define either a target or a role act like a queue.

    Wenzel, Toni supported this idea  · 

Feedback and Knowledge Base