I'm building a Java based project using Maven 3.0.3 with 100+ modules running TeamCity Enterprise 7.0.4 (build 21474), a single source file change results in long build and test phases due to Maven's incremental build handling. TeamCity's "Build only modules affected by changes" function is exactly what I'm looking for but it doesn't work when the project is split across multiple ClearCase VOBs and is based on a dynamic view.
I've created a mock project that highlights the issue, so if I have the following
If I change src in module1 TeamCity correctly triggers the build, evaluates affected modules and builds as expected. However, if I change src in module2 TeamCity correctly triggers the build but then does nothing and logs "No modules affected by changed files detected".
Has anyone experienced this and/or is this a known issue?