By "our CI" setup you mean last build on current machine, or doing 1.0 release builds on new AWS account.
Think @evans has the building of containers and general bigtop assets going. I believe there is still some work to setup final pass on new AWS account. After we can build the assets and packages, we can also setup some repos too -----Original Message----- From: Konstantin Boudnik [mailto:[email protected]] Sent: Friday, July 31, 2015 2:28 PM To: [email protected] Subject: Re: Gearing up for 1.0.0 (cut-off of the branch) I have rolled out RC1 and started the [VOTE]. Questions to Evans and Nate: do you guys think we can produce the binary packages once the release is accepted? It'd be nice to have them made on our CI setup, but I am not sure if this is possible at the moment. Thanks! Cos On Fri, Jul 31, 2015 at 01:46AM, Konstantin Boudnik wrote: > Started, finally, preparing RC1 and hit a few issues. Some of them > like > BIGTOP-1947 were easy to fix, but there's particularly one that I have > no idea what to do with: BIGTOP-1949 > > It seems that Sqoop's artifacts for sqoop-core and sqoop-client from > 1.4.5 (and 1.4.6) are pulled off the net hence the smoke test artifact > can not be build. If anyone has any insight into what's going on on > that from - please share. I am also cross-posting this to dev@sqoop so > hopefully they will be able to comment on the issue. Thanks for the help! > > Regards, > Cos > > On Sat, May 30, 2015 at 10:14AM, Konstantin Boudnik wrote: > > Ok, master is unlocked for 1.1.0-SNAPSHOT development I have also > > pushed branch-1.0 that has all the bits for 1.0 RC, but I don't have > > time to finish RC publishing up right now - will try to do it from > > the train, but who knows if I will have any connection there. > > > > If anyone can pick up where I left-off - it'd be great: I am really > > trying to get on my damn vacation ;) If not - I will try to find a > > bit of time next week for this. > > > > Thanks all for your help, > > Cos
