Hi Christian,
On 10/26/2013 09:28 PM, Christian Schneider wrote:
On 26.10.2013 21:14, Jean-Baptiste Onofré wrote:
Hi Christian,
- If you mean create two job in Jenkins, I disagree. I would prefer to
work with profiles. More over, it makes sense to tight the itest on
the artifacts that we just built before. Maybe we can have to target
on Jenkins: one with the itest profile, one without the itest profile.
The trigger for the full build (including itest) is every night, the
build without itest is at scm polling.
I did not want to have a build without itests. The itests are fast
enough to run in both builds. I wanted one build with itests after each
commit and one build with itests and deploy nightly. The problem
currently seems to be the deploy it takes much longer than the tests.
Catcha, so build without deploy after scm poll, and deploy only for
nightly builds ? I can do that.
- For the PerClass test on feature, I'm agree.
- Not sure I follow you for the PerSuite. What do you mean ?
PerSuite will start karaf only once and run several test classes on it.
Catcha, you mean reuse the same Karaf container for all itests. We just
have to be careful that one itest doesn't impact another. I have issues
like this when I implemented itests.
Regards
JB
Christian
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
