On 21 September 2013 22:25, Sergio Fernández <[email protected]> wrote: > Hi, > > > On 21/09/13 12:30, Peter Ansell wrote: >> >> The first step for me would be turning off incremental builds, and >> making each build a full build. > > > Incremental builds were disabled.
Okay, sorry, I can't see the configuration. The reason I thought that they were still incremental is that some of the modules are being fingerprinted by jenkins as originating outside of jenkins. That happened for me in the past with incremental builds, but there must be another reason in this case. >> That will make it easier to identify >> errors in the dependencies using the fingerprints. > > > In this case I guess is not due a wrong dependency, but an issue how the > tests are performed there. The tests executing aren't the biggest issue IMO. The fact that Jenkins isn't able to reliably compile Java files is a bigger issue (possibly due to the dependency resolution issues as manifested in the fingerprints). It may have been hidden for a while if contracts have been stable recently. Cheers, Peter
