Hi Olaf, The bigtop ci credential attached:
gpg -d oflebbe-ci.gpg > bigtop-ci.tar.gz Evans 2015-12-14 11:04 GMT+08:00 Evans Ye <[email protected]>: > Sorry for the fake fix yesterday. There were still some rotted data... > Anyhow the ci is back in good shape now and the nexus cache is working! > Thanks Olaf. > > Although, that hive build failure is wired... > > > Could not HEAD > 'https://plugins.gradle.org/m2/gradle/plugin/org/nosphere/apache/creadur-rat-gradle/0.2.0/creadur-rat-gradle-0.2.0.jar'. > Received status code 409 from server: Conflict > > > I'll step back and observe for a while. > > > 2015-12-14 3:38 GMT+08:00 Konstantin Boudnik <[email protected]>: > >> I believe GPG is the way to go, as Evans suggested. >> >> cos >> >> On Sun, Dec 13, 2015 at 12:30PM, Jay Vyas wrote: >> > Ditto thanks Evans! >> > Like Andy said we will need to follow up w passwords for the PMC. >> > >> > I don't know the "right" way to encrypt files, but I can hack a first >> pass together for review, unless someone else wants to try....? >> > >> > > On Dec 13, 2015, at 12:25 PM, Konstantin Boudnik <[email protected]> >> wrote: >> > > >> > > No worries and thanks for doing all this! >> > > >> > > Cos >> > > >> > >> On December 13, 2015 8:49:06 AM PST, Evans Ye <[email protected]> >> wrote: >> > >> Sure. >> > >> >> > >> Let me distribute the pem file to you guys so that, with AWS console >> > >> and >> > >> the private ssh key, you can have access to everywhere I can. >> > >> I'll enclose the info by your gpg key disclosed in BIGTOP-1762 and >> > >> send it >> > >> via mail separately, hang on there. ;) >> > >> >> > >> 2015-12-13 8:44 GMT+08:00 Andrew Purtell <[email protected]>: >> > >> >> > >>> Please make sure *all* credentials are each shared by several >> members >> > >> of >> > >>> the PMC. >> > >>> >> > >>> >> > >>>> On Dec 12, 2015, at 10:55 AM, Evans Ye <[email protected]> wrote: >> > >>>> >> > >>>> Sorry, I was away for some other business for a while. >> > >>>> >> > >>>> I've fixed the build slave. >> > >>>> The root cause is we were hitting device mapper 100G pool size >> > >> limit, >> > >>>> hence there's no space left for docker containers to run. >> > >>>> I see the build is currently running and it's good so far. >> > >>>> It's super late here, so please leave message and ping me if any >> > >>> additional >> > >>>> issue happened. >> > >>>> >> > >>>> 2015-12-12 15:38 GMT+08:00 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 >> > >>> >> > >
