Infrastructure code related changes done\in progress, related to this proposal, currently are maintained in a separate repo.
If this needs to be part of ASF, please let us know a suitable place to commit these changes. Its suggestible that all the infrastructure changes be part of a separate branch under CS, so that it is easy to maintain and use. Please let us know, so that we can create one and check them in to be made available to all. Regards, Santhosh ________________________________________ From: Alex Huang [alex.hu...@citrix.com] Sent: Tuesday, May 13, 2014 3:43 PM To: dev@cloudstack.apache.org Subject: RE: [PROPOSAL] Using continuous integration to maintain our code quality... Noji, Everything should be checked in under tools. I'll make sure of that. None of the code/configuration should be private. --Alex > -----Original Message----- > From: ynoj...@ynojima.net [mailto:ynoj...@ynojima.net] On Behalf Of > Yoshikazu Nojima > Sent: Tuesday, May 13, 2014 8:20 AM > To: dev@cloudstack.apache.org > Subject: Re: [PROPOSAL] Using continuous integration to maintain our code > quality... > > Alex, > > Thank you for interesting proposal. I suppose pre check-in test is long- > awaited for everyone. > I'm looking forward to see your Jenkins made public. > > If possible, can you share jenkins job's settings.xml for future reference > when it is ready? > > Regards, > Noji > > 2014-05-13 2:04 GMT-06:00 Daan Hoogland <daan.hoogl...@gmail.com>: > > Ritu, > > > > If I understood Alex' page on the wiki correctly you can run against > > your own fork. > > @Alex: true? > > > > On Wed, May 7, 2014 at 8:07 PM, Ritu Sabharwal <rsabh...@brocade.com> > wrote: > >> Hi Alex, > >> > >> I am a new developer (non-commiter) and getting to learn about the > development process of CloudStack. > >> > >> I have a question about the Jenkins, when you say create a branch for > your code and ask Jenkins to run BVT on your branch. The branch will be > created on my local repository but Jenkins would run on central repository. In > that case, does it mean that I install Jenkins locally on my setup. > >> > >> Please help. > >> > >> Thanks, > >> Ritu S. > >> > >> -----Original Message----- > >> From: Alex Huang [mailto:alex.hu...@citrix.com] > >> Sent: Tuesday, May 06, 2014 5:04 PM > >> To: dev@cloudstack.apache.org > >> Subject: [PROPOSAL] Using continuous integration to maintain our code > quality... > >> > >> 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 > r > >> ocess > > > > > > > > -- > > Daan
