[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21145: ------------------------------------ {quote}why keeping the composite builds?{quote} In addition to it being a handy way to orchestrate running both the JBT core and core-tests jobs in parallel, it also verifies that the contents of the composite can be co-installed. Sure, we have additional tests that do install tests downstream of the JBT aggregate build, but this is the *first-line verification* that we don't have some incomplete change (eg., an API change in Base that hasn't been absorbed by Server, or a change to JST which points to the wrong version of AngularJS). And while it can be annoying sometimes when the job fails, it's better than relying on the install-grinder test, which is often broken for months w/o anyone repairing it. A 3-day problem is way better than a 30-day one, since people SEE it and complain. IMHO, the system is working because we blocked the build when a test failed. Isn't that how test-driven dev is supposed to work? :D -- This message was sent by Atlassian JIRA (v6.4.11#64026)