On Sat, Jan 09, 2016 at 12:25PM, Evans Ye wrote: > Bigtop-trunk-packages is about to back in business, I guess. > > We just need to comment out: > > #docker run --rm -v `pwd`:/ws --workdir /ws -e COMPONENTS=$COMPONENTS > --net=container:nexus bigtop/slaves:trunk-$BUILD_ENVIRONMENTS \ > #bash -c '. /etc/profile.d/bigtop.sh; ./gradlew allclean ; ./gradlew > configure-nexus $COMPONENTS-pkg' > > It seems running well now: > http://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages/ > > > > Hey Olaf, > I've a question, can't we start a nexus server on CI master for permanent > and then add the repository for each build?
I think having a local mirroring Nexus server - either per the whole build, or just standalone, might be very beneficial for the build time/failure rates. Cos > 2016-01-09 4:32 GMT+08:00 Konstantin Boudnik <[email protected]>: > > > On Fri, Jan 08, 2016 at 09:22PM, Olaf Flebbe wrote: > > > Hi > > > > > > I am talking about Bigtop-trunk not Bigtop-trunk-packages. > > > http://ci.bigtop.apache.org/job/Bigtop-trunk/ > > > > Oh, my bad, sorry. Packages are a part of our CI pipeline and serves a > > different purpose of course. > > > > > That's the all-in-one thingy- opposed to the great visualisation of > > packages > > > vs operating system matrix. > > > > > > I tried several aproaches to create a repository out of > > Bigtop-trunk-packags > > > but it turned out really complicated. Bigtop-trunk already generates > > > > Yeah, there's a bit hurdle with that. I have shared a link to a couple of > > scripts I've put together for a project I am doing, which essentially > > allows > > to collect together all the packages from the dockerized build and then > > create > > the repos. > > > > For the release (RC or whatever) we should use the Bigtop-trunk of course - > > it's a one-off build essentially. I think this is what Evans have done to > > build 1.0.0 binary artifacts. > > > > Thanks! > > Cos > > > > > repositories, so I suppose we should carve 1.1 repositories out of > > > Bigtop-trunk rather assembling back the artifacts of > > Bigtop-trunk-packages. > > > See for instance: > > > > > http://ci.bigtop.apache.org/job/Bigtop-trunk/BUILD_ENVIRONMENTS=debian-8,label=docker-slave/lastSuccessfulBuild/artifact/output/apt/ > > > > > > Olaf > > > > > > > > > stantin Boudnik <[email protected]>: > > > > > > > > > > > > I might be color-challenged %) then > > > > > > http://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages/ > > > > > > > > cos > > > > > > > > On Fri, Jan 08, 2016 at 06:43PM, Olaf Flebbe wrote: > > > >> Hi, > > > >> > > > >> updating the CI Infrastructure made Bigtop-trunk all blue. > > > >> > > > >> I will disable the nexus workaroung now for Bigtop-trunk-packages . A > > new bigtop/slaves:trunk-opensuse-13.2 image is pushed > > > >> > > > >> > > > >> Olaf > > > > > > > > > > > > > > > > >
signature.asc
Description: Digital signature
