I have a build configuration that depends on 3 other build configurations, but the order of how it builds matters, but those build configurations does not depend on each other. It seems to me, that the order depends on speed. The quickest build runs first and the longest build runs last.
Is there a way with multiple build configurations to running at the same time to set a priority in which ones gets to build first?
Also, is there a way to to prevent other build configurations from triggering if one particular build is running. For example, I have the App and data built on a server build agent, but can only be run on a work station build agent. What I did was I created a shared directory so that the workstation build agent can run it. However, it can still sync new changelist and rebuild while it's running. I want to lock it so that when the app is running, it will not sync or build i.e. it waits for the run to complete before syncing and rebuilding.
I guess an alternative solution which i got working was to deploy that built apps and data to the workstation when its done and run it locally instead of running it off the shared directory.
Any help would be much apprieciated.