RB

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    RB shared this idea  · 
  2. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    RB shared this idea  · 
  3. 355 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    RB commented  · 

    Please add this. Many of our deploys are on Windows and there are so many things that can go wrong where a simply retry, just once, seems to correct it. To get around this issue, we've had to add our own custom retry methods which have helped a lot but we still have many step templates to port over. It would be so much more convenient and scalable to have this built into octo.

    RB supported this idea  · 
  4. 67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    RB commented  · 

    If there was a new key in the event json called QueuedBy, we would also be able to see which events were initiated originally by a human vs the system user. This would be helpful in non DeploymentQueued events like Succeeded, Failed, etc.

    RB supported this idea  · 
  5. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    RB shared this idea  · 

Feedback and Knowledge Base