Hi, The correct way would be to start Bigtop-trunk-packages-nexus-start
than Bigtop-trunk-packages and to finish with Bigtop-trunk-packages-nexus-stop -- But the docker-slave-06 ist still out of order and someone (Evans?) is working on it. Olaf > Am 12.12.2015 um 08:38 schrieb Konstantin Boudnik <[email protected]>: > > Ok, I think the slaves are back now and I have enabled the nexus job, but > still the package builds are failing because of unknown id nexus. > > Not sure what's next and it is almost midnight here, so my brain doesn't > function well ... > > Cos > > On Fri, Dec 11, 2015 at 11:43PM, Olaf Flebbe wrote: >> Hi, >> >> I changed the build of bigtop-trunk-packages to have a pre job >> bigtop-trunk-packages-nexus-start to be run on all node via a label-plugin >> and a bigtop-trunk-packages-nexus-stop to clean up afterwards. >> >> unfortunately the docker daemon on docker-slave-06 is unresponsive , so I >> decided to disable bigtop-trunk-packages-nexus-start >> >> If someone with a root passwd please reboot the docker-slave-06 node and >> enable bigtop-trunk-packages-nexus-start ... >> >> Olaf > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
