Daan, I think every part of the proposal is up for discussion and suggestions. It's why I put it on to the list for everyone to review.
For the concern on distributed setup, there's a two part answer. 1. We're basically asking everyone to use a central Jenkins to run the automated before they merge to the asf git repository to make sure they didn't break the product for everyone. It shouldn't have any impact on your local Jenkins. It's perfectly fine for to run all tests yourself for the majority of your code/build/test cycle and only run one sanity test when submitting to the asf git repo. Note that we're only asking this for the master and the currently releasing branch. Your remote branches are yours only. 2. All of the software that we wrote/using are checked into the asf git repo, we welcome anyone to set this up for themselves if you need something more speedy. If you do set it up, then I don't see why you need to use the service that is proposed here. As for reviewers, I'm open to the number of reviewers. The only number I will be against definitely is zero. My personal opinion is that the quality of the reviewer is more important than the quantity. I'm not sure how we can make sure the quality of the reviewer is good. I'm open to suggestions there. The page itself is still being updated. Some of the links need to be cover in more detail and some links need to be updated. I will continue to update the list. --Alex > -----Original Message----- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Wednesday, May 7, 2014 3:34 AM > To: dev > Subject: Re: [PROPOSAL] Using continuous integration to maintain our code > quality... > > Alex, > > I applaud the effort and everybody at Citrix contributing to it. > This is not a concern with your proposed process: I hope it does not impede > the efforts to have a distributed setup where everybody can start their tests > specific to their hardware from the central jenkins on their local jenkins > slaves. > One concern that I do have is the finding of two reviewers. I think we can ask > of people to put effort into finding two reviewers but it is my experience > that > these are not always available/willing/able to make time. > The page you made looks good. You could add link in the list of 'developer > resposibilities' to relevant documentation. > > kind regards, > Daan > > On Wed, May 7, 2014 at 2:03 AM, Alex Huang <alex.hu...@citrix.com> > wrote: > > Hi All, > > > > This is something I brought up a long time ago but really didn't have the > resources to get it all up and running until now. Throughout the past year, > Edison, Prasanna, Amogh, Bharat, Koushik, Talluri, and others have been > chipping away at it. At this point, we finally pull together a continuous > integration setup that we can use to make sure that CloudStack master and > the currently release branch are always stable. This is getting pretty close > to > be completed and we like to share it with the community in hopes that we > can reduce/eliminate that problems we've seen with our recent releases. > Currently, the physical hardware are hosted by Citrix but we'll be more than > willing to donate the work to infra when that's all settled. > > > > This does require effort from the community to make a change in their > development process. These steps are detailed at [1]. I like to get feedback > on what everyone think about this. > > > > What have we done: > > - We replaced a large selection of the BVT tests to run with the simulator > instead of actual hardware. This shortens the duration of each BVT run. > Today, a BVT that runs tests for XenServer and KVM completes in 30-40 > minutes. > > - We will run the new BVT on master and the current release branch on a > continuous basis. > > - Developers can use Jenkins to ask BVT to be run on their branch so they > can know it won't break the continuous integration before they merge to > master and the current release branch. > > > > Please have a read and let me know what you think. > > > > --Alex > > > > [1] > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Development+P > ro > > cess > > > > -- > Daan
