Hi folks, Allow me to report some progress on our CI settings for 1.0 release. ([email protected] asked me about the status and would like to help but sorry I didn't respond you well back then)
For 1.0 to release, we need to build bigtop by those supported OS listed in BIGTOP-1480. And I plan to use use docker images to build 1.0 release directly so that we don't need to setup jenkins slaves one-by-one. (the fastest way I can think of for speeding up 1.0 release) My plan is to prepare bigtop/puppet images by ourselves <https://github.com/evans-ye/bigtop-dockerfiles>and apply bigtop_toolchain by jenkins <http://bigtop01.cloudera.org:8080/view/Docker/job/Docker-Toolchain/>to get bigtop/slaves images. I've built and tested some of the OS in bigtop/puppet family (stored as evansye/puppet <https://registry.hub.docker.com/u/evansye/puppet/tags/manage/>temporary), but some of the OS do not work properly since I'm lacking of knowledge on them. ***worked*** centos-6 centos-7 ubuntu-14.04 (unchanged) fedora-20 (unchanged) ***not working*** opensuse-13.2 ---> I can't have "hostname" package installed, it seems that is needed by puppet to determine what node to apply debian 8 ---> no wget and curl available [root@bigtop ~]# $ docker run -ti --rm debian:8 bash -c 'apt-get -y install curl wget' Reading package lists... Done Building dependency tree... Done E: Unable to locate package curl E: Unable to locate package wget Todo list: 1. It would be a great help if opensuse and debian expert can come to help on those issues. 2. I'd like to have the credential for bigtop dockerhub so that I can put new OS images on it. 3. Have all package in trunk built by new Docker slaves Maybe Roman can help me out on *#2. :)* You can enclose me the credential by my pgp: curl http://people.apache.org/~evansye/evansye.pgp That it. Suggestions are welcome! Thanks, Evans 2015-03-31 7:09 GMT+08:00 Konstantin Boudnik <[email protected]>: > Currently all the slaves shut-down: looks like the instances have been > turned > off as I can not relaunch the slaves. Will try to restart them tonight > once I > am on machine with AWS keys. > > Cos > > On Tue, Mar 24, 2015 at 06:06AM, Konstantin Boudnik wrote: > > Guys, > > > > I want to start a separate thread to track the CI preparations for the > release > > next month (fingers crossed). Clearly, we can make a release without CI, > but > > it'd way easier to test and create binary artifacts if we have a working > > environment for official validation. Roman has done a lot in this > direction > > (many thanks!), but there are still a few rough edges, which might be > easy to > > finish of. > > > > I want to figure out a couple of things: > > - what's the state of CI and how much still needs to be done (Rvs? > Could you > > share any first hand feedback?) > > - who would be able to help with the CI completion? I can commit some > of my > > cycles, but it'd be great to have few more hands on that. Clearly, > some > > Jenkins-foo and prior CI skills won't hurt ;) > > > > Please chime in if you can help. Thanks a lot! > > Cos > > >
