We're curious to know whether you plan to implement (or already have) something
that could help with the following scenario:
We have the following build setup:
- a build config that gets triggered by changes in the java source tree.
It compiles the code and runs the unit tests. Some of the tests involve DB
- a build configuration that monitors the DB subtree of the source code and,
when finding changes there, it updates the DB scripts and runs a DB update
with the new DB scripts. After that, a dependency build for the java unit
tests is triggered.
The following "conflict" is encountered every now and then: while the java
unit tests build is running, somebody checks in some DB related stuff. The
DB build is triggered and the running java build is messed up by the db changes.
Can some sort of wait dependency be provided? Something that would prevent
a build config from running while another one is in progress?
Is it to late to request such a feature for the next release?