Hi As some of you might already have noticed most of the recent Jenkins builds have timed out.
https://builds.apache.org/job/stanbol-trunk-1.6/ I have monitored a build on Monday and the conclusion is that the Archiving step of big artifacts do need most of the time (actually I think this takes nearly all of the time). This corresponds to log entries like [JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/stanbol-trunk-1.6/trunk/commons/solr/core/target/org.apache.stanbol.commons.solr.core-0.9.0-incubating-SNAPSHOT.jar to /home/hudson/hudson/jobs/stanbol-trunk-1.6/modules/org.apache.stanbol$org.apache.stanbol.commons.solr.core/builds/2011-11-01_15-04-57/archive/org.apache.stanbol/org.apache.stanbol.commons.solr.core/0.9.0-incubating-SNAPSHOT/org.apache.stanbol.commons.solr.core-0.9.0-incubating-SNAPSHOT.jar This is supported by the fact that the build times for the modules are directly related to the size of the resulting artifact (launchers do have the longest build times, followed by the default data bundle and other bundles that include a lot of jar files - such as the sold.core bundle). Maybe one could check if this archiving state can be disabled - so that only the results of the last build are accessible via the workspace. If this is not possible an other workaround would be to deactivate the building of some of the launchers (in principle only the full launcher is needed by the integration tests). In addition to that I would suggest the following thee changes to the Jenkins configuration: * switch form maven 2 to maven 3 because I think that maven 3 is now the default maven version used by most Stanbol devs. (this should also help to speed up build times a little bit) * include windows builds (to check that utilities like the DataFileProvide do also function correctly on Systems running some Windows OS) * deploy SNAPSHOT builds on the Apache snapshot maven server (similar as Clerezza does). Retro was mentioning that this can be done by changing the Jenkins configuration accordingly. WDYT Rupert
