Le 20/12/15 20:07, Stefan Seelmann a écrit : > Hi devs, > > just a quick status update to our Jenkins jobs: > > * ApacheDS and Studio jobs currently fail because of not yet published > API and ApacheDS versions, so please ignore those failures for the next > day or two.
Okie, fine > > * Kerby build fails for some days, problem is that snapshots cannot be > deployed to Nexus. > > * Fortress Docker tests fail for some days, there are 5 test failures. I'm looking at https://builds.apache.org/view/A-D/view/Directory/job/dir-apacheds-docker-installers/lastBuild/console, and the error is not obvious. Typically, the build is a success : ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:33 min [INFO] Finished at: 2015-12-16T02:55:21+00:00 [INFO] Final Memory: 153M/485M [INFO] ------------------------------------------------------------------------ [dir-apacheds-docker-installers] $ /bin/bash /tmp/hudson5347829253313480382.sh ... + service apacheds-2.0.0-M21-SNAPSHOT-default start Starting ApacheDS - default... + wait_for_apacheds + timeout 15 sh -c 'while ! nc -z localhost 10389; do sleep 1; done' Build step 'Execute shell' marked build as failure Archiving artifacts Sending e-mails to: [email protected] Finished: FAILURE May be the 15s time out is not enough ? > > All our jobs can be found at [1], so please have a look. > > Please note that build failures are mailed to > [email protected], so if you are not subscribed to > please do so. Or does it make more sense to send Jenkins notifications > of Kerby and Fortress to the kerby@ and fortress@ respecitve? No, [email protected] makes sense. Otherwise we would be polluted... Many thanks Stefan !
