On 22 September 2013 07:06, Peter Ansell <[email protected]> wrote: > 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.
Is Maven in Jenkins being run without the clean goal? The logs have the following message: "Executing Maven: -B -f /home/jenkins/jenkins-slave/workspace/Marmotta/pom.xml -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/0 install " I would have expected that to have "clean install" at the end, to ensure that any old target directories did not interfere with the process. Not having "clean" there may be what caused me to think it was an incremental build, btw. You could also try clearing out the workspace, as it still has the JSON-LD and RDF/JSON modules in it, although they are not run. " Sesame I/O: JSON/LD (didn’t run) Sesame I/O: RDF/JSON (didn’t run)" Debugging this would be a little easier if I could see the Jenkins configuration as it is a little difficult to guess what the settings are sometimes just based on the logs. Cheers, Peter
