cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Huang <>
Subject RE: [PROPOSAL] Using continuous integration to maintain our code quality...
Date Tue, 13 May 2014 19:41:52 GMT
Actually, this email was sent twice and I answered the first time it was answered.  The short
answer is yes, everyone can request the CI to be run on their own branch and they must do
that before merging it into the release/master branch.  Here's my answer enclosed in case
it was somehow missed.

" Hi Ritu,

Citrix will provide a Jenkins server that's public accessible that enables you to request
BVT to be run on your branch.  You don't need to install one yourself.  When ASF infra is
ready with their hardware, the scripts can be donated to ASF and then developers will need
to switch over to the Jenkins operated by ASF.

As for contributors, I did leave out one important part.  We will try to allow for the code
to be pulled from github but that might come after CI is made available.  For now, you'll
have to submit your patch through review board and let the reviewer put it through CI for


> -----Original Message-----
> From: Daan Hoogland []
> Sent: Tuesday, May 13, 2014 1:04 AM
> To: dev
> Subject: Re: [PROPOSAL] Using continuous integration to maintain our code
> quality...
> 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 <>
> 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 []
> > Sent: Tuesday, May 06, 2014 5:04 PM
> > To:
> > 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]
> >
> ro
> > cess
> --
> Daan
View raw message