[node-devel] Jenkins Builds

[Mike Burns]

I forgot to mention trigger intervals.

ovirt-node-devel and ovirt-node-stable will be triggered automatically
by patch submissions and commits being merged, respectively.

ovirt-node-iso is triggered by a successful build of ovirt-node-stable,
a commit to the ovirt-node-iso repository, and a nightly trigger at 1:01
AM EST/EDT.

ovirt-node-iso-devel is triggered by successful builds of
vdsm-create-rpms and ovirt-node-devel, a commit to the ovirt-node-iso
repository, and a nightly trigger at 1:01 AM EST/EDT

Mike 

On Fri, 2012-03-16 at 15:20 -0400, Mike Burns wrote:
> http://jenkins.ovirt.org/view/ovirt_node/
> 
> From the above page, there are now 4 builds listed:
> 
> ovirt-node-stable
> ovirt-node-devel
> 
> These will build the ovirt-node and ovirt-node-tools rpms based on the
> git repo from gerrit.ovirt.org.  Currently, both are building from the
> tip of the master branch.  Once the gerrit trigger plugin is fixed, the
> -devel build will build with each patch posted to gerrit for review.
> 
> ovirt-node-iso
> ovirt-node-iso-devel
> 
> These will build ovirt-node ISO images and RPMs.  
> 
> ovirt-node-iso will build based on the ovirt-node-stable ovirt-node rpms
> and the latest vdsm found from either ovirt.org/releases/stable or
> fedora update repos.
> 
> ovirt-node-iso-devel will build using the ovirt-node-devel rpms and the
> vdsm rpms from the vdsm-create-rpms job in jenkins.  The
> ovirt-node-devel rpms contain non-verified patches.  The vdsm build
> contains merged patches that aren't in the latest official packages.
> 
> Let me know if there are any questions.
> 
> Mike
> 
> _______________________________________________
> node-devel mailing list
> node-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/node-devel