Settings and activity
5 results found
-
1 vote
RB shared this idea ·
-
2 votes
RB shared this idea ·
-
215 votes
An error occurred while saving the comment RB supported this idea ·
-
29 votes
An error occurred while saving the comment 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 ·
-
1 vote
RB shared this idea ·
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.