On 25/02/2012, at 11:31 AM, Szczepan Faber wrote: > If there are no objections I'd like to make the full compatibility suite > tests (e.g. all supported previous versions) a nightly build. The check-in > build will still run the compatibility tests but with limited number of > versions (e.g. current master and currently released). This applies to the > tooling api tests and CrossVersionIntegrationSpec. > > I'm pretty sure it's a good move wrt tooling api. I'm not 100% sure about > CrossVersionIntegrationSpec. Let me know :)
I think this is a good thing to do, except perhaps we move the tests to a triggered build (like the daemon test suite), rather than a nightly build. We also want some coverage for the full test suite on windows as well as linux, and probably java 5, 6 and 7, ibm jdk, etc. So, perhaps what we're talking about instead is a new build that slots in before the existing commit builds, and triggers them on success. Some other things to get faster feedback: * Run DistributionIntegrationTest less often. This is effectively a test for the build itself, so we only need to run it when we're releasing, building a snapshot, and perhaps in one CI build. * We should fix http://issues.gradle.org/browse/GRADLE-1939. This is a quick fix and will knock a couple of minutes off the tooling api samples tests. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
