I think Nate answered most of the questions, so thanks a lot! To me the most critical task is to have 1.0 released, while CI overhaul is part of the task. >From my point of view, there're two thinks holding us back from release.
1. The 1.0 branch is still at bleeding age to support all the claimed OSs. The primary issues are in debian(should be fixed now) and oepnsuse working as bigtop build slaves. 2. Migrating the CI master to EC2 under EMR donated account. Since I can't get in the old CI master, there's no way for me to retrieve current job configs and restore them back to new CI master. Roman probably has backups but he might be busying on other things. 3. I'll let cos add more since I'm not quite familiar with release criteria, but I'd love to help. I guess we can't have 2 solved in short period, so I might start to work on setting up repositories on old CI master directly. Thanks, Evans 2015-06-27 3:46 GMT+08:00 <[email protected]>: > Still work in progress, will let Evans add some more details as he has been > the one kickin but on CI tasks. Besides some more setup and planned > enhancements focus is getting 1.0 out the door, then turning towards more > foundational CI work for 1.x and beyond. > > Think we will be well served having more official bigtop repos serving, I > setup a prototype off 0.8, serving from S3.., few things for us to figure > out build/process wise to properly hook the CI into S3/repo publishing > > Evans created this jira for general tracking: > https://issues.apache.org/jira/browse/BIGTOP-1897 > > Not all of which are required for new CI to be ready, for example newly > added one for optimizing build process to reuse artifacts can start working > on in parallel to new CI and 1.0 release but get completed after both are > taken care of > > -----Original Message----- > From: Zeng, Tom [mailto:[email protected]] > Sent: Thursday, June 25, 2015 3:36 PM > To: Evans Ye; Konstantin Boudnik > Cc: [email protected] > Subject: Re: Brand new Bigtop AWS account > > Hi Evans and Cos, what's the status of this, do we have the build CI > environment set up yet? > > Thanks, > Tom > > From: Evans Ye <[email protected]<mailto:[email protected]>> > Date: Sunday, April 19, 2015 at 11:12 AM > To: "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>>, "Zeng, Tom" > <[email protected]<mailto:[email protected]>> > Subject: Re: Brand new Bigtop AWS account > > Hi guys, > > I've copied security group settings from the old account to the new one > provided by EMR team (thanks Tom!). > I've also checked our existing jenkins and there are some useful jobs > already defined. It seems that I only need to have some slightly > modification on them to get it start working. > My plan is to create a m3.xlarge instance and directly plug it on our > existing jenkins as a slave so that I can start to make some progress. > I'll keep you posted. Suggestions are welcome as well. :) > > Thanks, > Evans > > > 2015-04-09 13:52 GMT+08:00 Konstantin Boudnik > <[email protected]<mailto:[email protected]>>: > Cycling back: today we got a credit coupon from Amazon EMR team so we have > everything to start building new CI infra. Please contact me directly if > you > plan to help with setting it up, so I can create an account with proper > permissions for you. > > Special thanks are going to Tom Zeng and his team for making it happen! > Thank you very much guys! > > 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 > > > > >
