Settings and activity
6 results found
-
16 votes
-
1 vote
Shane
shared this idea
·
-
15 votes
An error occurred while saving the comment Shane
supported this idea
·
-
2 votesShane
supported this idea
·
-
68 votes
Until we implement this feature, the work around would be to monitor the deployment using the API and cancel it if a timeout has been reached.
I have written up a script (https://octopus.com/blog/automating-octopus-with-azure-functions) that retrieves all running deployments for a project and cancels it if:
- it has been running for more that 30 minutes
- the first step has been running fro more than 20 minutes
- the first step has not output any logs in 5 minutesThis can run as a scheduled task. Alternatively you can use the subscriptions feature to kick off a piece of code (eg Azure function) that does this polling, as described in this blog post: https://octopus.com/blog/automating-octopus-with-azure-functions
— Robert W
An error occurred while saving the comment Shane
commented
Can someone please confirm if this is still outstanding? I'm not seeing any solutions although I am on a 2019.12 build.
Shane
supported this idea
·
-
148 votesShane
supported this idea
·
The ability to target different roles for child steps seems like such a trivial enhancement but it would remove a lot of unnecessary duplication.
I've a project that powers on a few dozen Azure VMs, checks their tentacle health and restores them to normal service. The problem with this is that, for any reasonable number of VMs, those that start early are waiting on the last ones to start before moving on to the health check and undrain steps; I’d like to use child steps to enable concurrency. When you’ve multiple environments and different types of target, running this concurrently becomes harder than it should be in Octopus; whilst I could achieve this with cloned parent steps, the optimal process would be one where I can set the targets within the child steps and not have Octopus enforce the scope of the parent step.