Martyna Wojtas (Inactive) added a comment - 07/Apr/2020 2:31 PM Atlassian Update - 7 April 2020 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.   Thank you, Bamboo Team

Ken Wood added a comment - 26/Sep/2012 3:19 PM Here is my use case: I have a resource shared across several build plans. Each build plan needs exclusive access to the resource. I cannot use agent capabilities and job requirements 'trick' to control access to the resource because, across the different stages of the build plan, a number of different remote agents need to be used. I could use a semaphore file approach to lock access to the resource via a script at the beginning of the build, and unlock it at the end of the build. But, if the build fails somewhere in between or if the build is stopped, the resource would never be unlocked. I could add 'final task' to every job to release the resource, but then in the next stage I would need to re-acquire the resource. That leaves open the possibility that, between the task that released the resource and the task the re-acquires it, another build plan that was waiting on the resource could acquire it instead, disrupting this build plan. Thus, I really need an action PRE the first stage of the build that can acquire lock on the resource, and a POST last stage (regardless of build success or failure) that can release the resource.