During build, our build server deploys to a testing server and runs various tests. If two different branches of the same configuration run simultaneously, both branches try to deploy to the testing server at the same time, and so they step on each other.
Is there a way to mark a configuration so additional builds of the same configuration will stay queued until the previous build completes? Simultaneous builds of different configurations is fine, just not of the same configuration. I can't find a way in the program or documentation to achieve this. I thought I could set a queue condition, but I can't find a property to key off of.
It would also work if we could restrict a stage to only have one simultaneous build.
It can’t be done at the moment, because the number of running builds/stages is not exposed to the object model used to evaluate conditions. I had a quick look at this, and at first glance it looked simple, however it’s possible for other builds (of the same config) to start executing while the conditions are being evaluated, and then I ended up with more builds running than I allowed in the conditions. I will need to do some further investigation on this.
The good news is we now have this working We’ll do some more testing on this tomorrow and hopefully it will make it into tomorrows build (we have a few other fixes to test before a build is ready). The functionality will be available through configuration conditions.