I've done a bit of cleanup: There are views for each active branch now (currently 4.0/master). 4.0 will be the default view until the release.
Since mvn will be the de-facto choice in the future we'll call the mvn builds as just: build-<branch>. Hence we have build-4.0 and build-master. No -cloudstack, -maven to reduce redundancy. For packages we have: build-master-rhel63 build-master-ubuntu1204 For non-oss components we add the infix-ed 'nonoss' build-master-nonoss-rhel63 Test jobs will start with test-<branch> so we'll have test-junit-4.0 etc Most importantly - docs are put into apidocs-<branch> docs-<branch> (publican guides) Hope that clears the views a little -- Prasanna., On Thu, Sep 20, 2012 at 10:06:12AM -0400, Chip Childers wrote: > On Thu, Sep 20, 2012 at 9:53 AM, Prasanna Santhanam > <prasanna.santha...@citrix.com> wrote: > > On Thu, Sep 20, 2012 at 09:18:32AM -0400, Chip Childers wrote: > >> The verify-licensing-master job is currently tied to the > >> build-cloudstack-master-maven job, which is not disabled. What's the > >> right parent job now? > >> > >> -chip > > > > Ah yes - my mistake. The last build was just aborted. > > > > Can the licensing job run for all branches? Most importantly > > should be set for the release branch - 4.0 - right now. > > Sure, as long as we have the space for it. However, I would like us > to ensure that we are getting early warning indications from master as > well... no reason to wait for the commits to be cherry picked over to > 4.0. > > > I can't seem to find the job that does mvn build alone. This should be > > the parent job for license verification. > > Right, that's what I had it tied to previously. I would have expected > that the Junit stuff was tied to that as well. > > > If we could stick to some rule for jobs: > > > > Something like the following? > > > > * cs-<branch> (Just a mvn build) > > ** cs-license-<branch> (license verify) > > ** cs-junit-<branch> > > * cs-<branch>-<package=rpm|deb> > > * cs-apidoc-<branch> > > * cs-doc-<branch> > > * cs-marvin-<branch> > > > > Each branch can have it's own view to make it clearer. Suggestions? > > I'm very much in favor of that. I actually created the orig 4.0 view > for just that reason. >
