Am 29.08.2013 08:45, schrieb Massimo Lusetti:
Is it possibile to "fix" this behavior ?
There are several options:
* configure Jenkins to run the clean task first
* configure the test task to never be up-to-date
* add a task that touches all test outputs [1]
There is obviously a trade-off between speed and reliability.
Running clean every time means that the whole source is re-compiled and
re-tested for every little change.
Touching only the test outputs might lead to old test output files being
picked up even though the tests are gone.
Jochen
[1]
http://www.practicalgradle.org/blog/2011/06/incremental-tests-with-jenkins/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
