I’m intersted in helping with the CI setup. Any pointers on where we stand today would help to take it forward.
On 3/24/15, 1:13 AM, "Evans Ye" <[email protected]> wrote: >I can help since I'm currently setting up our CI environment as well. > >But just as what cos said I'd like to know what's the current situation >and >what's the goal we're heading to. >Here's one of what I think we need to have: setup a jenkins job that >provision bigtop cluster by docker provisioner and run smoke-tetsts and >integration tests on top of it, then collect and draw the testing results >on jenkins so that we can clearly know what component is broken either in >the deployment stage or in testing stage. > >The password or credential for bigotp CI environment might also be needed, >I think BIGTOP-1762 ><https://issues.apache.org/jira/browse/BIGTOP-1762> password >pgp files can help. > > >2015-03-24 15:48 GMT+08:00 Bruno Mahé <[email protected]>: > >> What kind of help are you looking for? >> I have very few spare cycles, so i cannot commit much. But I can keep an >> eye on it. >> >> >> On 03/23/2015 11:06 PM, 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 >>> >>> >>
