On Wed, 2014-12-17 at 10:25 +0100, Carsten Ziegeler wrote: > Am 17.12.14 um 10:14 schrieb Stefan Seifert: > > it seems that what fails are mainly different integration tests. > > > > we could add a special maven profile in those projects that have failing > > integration tests that disables the IT in only that project, and create a > > ticket for each project to track that we remove it when the IT problem is > > solved. on Jenkins this profile is enabled so these problematic ITs are > > skipped by default, but not when running them locally withouth the profile. > > > > those integration tests are not only problematic on jenkins, i have > > problems running them with windows as well. a starting point before > > analyzing deeper the root cause of the failing might by updating the > > involved testing tools, e.g. sling testing tools, pax exam etc. the ITs use > > quite different version currently. > > > Right, this could help, but I also have the feeling that many jobs fail > just because of some Jenkins wiredness or whatever.
I know of one failure scenario - the one where the job is killed. I'll try and follow up with infra today. Typically I file tickets at [1] and the infra team makes sure they are solved in a relatively timely manner. > So what about disabling all jobs on Jenkins, and enable just one and try > to get that one running clean, then we can enable the next one etc.? That would be good - we could keep only sling-trunk-1.6 enabled and see where that takes us. > > Carsten [1]: https://issues.apache.org/jira/browse/BUILDS
