You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have forked this resource to support a "max_minutes" attribute used to (unceremoniously) move claimed locks back to unclaimed if it is held for longer than this threshold. Perhaps this would be a desirable feature in the standard resource. We perform this clean-up as follows
1- Perform cleanup from "check" since the ATC runs only a single instance of this at a time
2- Check the timestamp of the last commit that touched this lock
3- If the max_minutes threshold is exceeded, unclaim the lock
3b- If the "unclaim" operation fails due to a (very possible) conflict, do not retry until the next check (to keep check running relatively quickly)
The text was updated successfully, but these errors were encountered:
For people with this need (detect and release stale locks after a timeout), you might want to have a look at our Pool Boy https://github.com/Pix4D/concourse-pool-boy, which is meant to run as a separate pipeline.
We have forked this resource to support a "max_minutes" attribute used to (unceremoniously) move claimed locks back to unclaimed if it is held for longer than this threshold. Perhaps this would be a desirable feature in the standard resource. We perform this clean-up as follows
1- Perform cleanup from "check" since the ATC runs only a single instance of this at a time
2- Check the timestamp of the last commit that touched this lock
3- If the max_minutes threshold is exceeded, unclaim the lock
3b- If the "unclaim" operation fails due to a (very possible) conflict, do not retry until the next check (to keep check running relatively quickly)
The text was updated successfully, but these errors were encountered: