I do agree that at the moment Travis is either creating false sense of security when it is green, or a burden for contributors when it is red, because most of the time it goes red for no good reason.
However, I would still find it valuable to have travis run a single command: mvn clean isntall -P developer,systemvv That is because, still many people commenting on PRs don’t even do that. In addition this would be faster than the Jenkins build, so it would provide faster feedback. Cheers, \ Miguel Ferreira mferre...@schubergphilis.com<mailto:mferre...@schubergphilis.com> On 29 Oct 2015, at 10:41, Remi Bergsma <rberg...@schubergphilis.com<mailto:rberg...@schubergphilis.com>> wrote: +1 it doesn’t help like this. I look at actual test result people post combined with code reviews. Plus an OK from Jenkins should be more than enough to judge a PR. Let’s make Jenkins more reliable, that would help as well. Regards, Remi On 29/10/15 10:33, "Daan Hoogland" <daan.hoogl...@gmail.com<mailto:daan.hoogl...@gmail.com>> wrote: Guys and dolls, We have been having travis builds for a while now and they seem to generate more work then help. There are a lot of time-outs, (false positive) and when a suite passes it is often because all tests where skipped (false negative). In addition, and this may be just me, I've never been able to pinpoint a problem based on travis output. therefore: I move that we completely disable travis runs on PRs to the cloudstack project. This will reduce confusion about whether a PR is good and will reduce the need for willing contributers to force push their branch over and over. -- Daan
