[node-devel] oVirt Node + VDSM Jenkins builder

[Fabian Deutsch]

Am Mittwoch, den 26.02.2014, 12:01 -0500 schrieb Ryan Barry:
> Adding a single plugin to the image should be much less troublesome
> than 
> the jobs we had which built an ISO on every commit, but I'd like to 
> avoid overloading Jenkins as much as possible while still fulfilling
> the 
> intended goal.

[Adding Douglas]

Hey,

yeah I think that is really the way to go, as edit-node is also our
recommended way to add plugins to an ISO.

> Looking at the build history of ovirt-node-plugin-vdsm, I don't think 
> that it would be too invasive to trigger this new job on completion
> of 
> ovirt-node-plugin-vdsm, but I'm open.

Yes, I agree on that. We should basically create a new iso once a new
ovirt-node-plugin-vdsm has been build.

Is there already a job which builds ovirt-node-plugin-vdsm?

Oh - And just to confirm - are we still planning to only add the plugin
to the last _stable_ base image?

- fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20140226/636a141d/attachment.sig>