Content-Type: text/plain; charset="UTF-8"
Am Mittwoch, den 26.02.2014, 12:01 -0500 schrieb Ryan Barry:
Adding a single plugin to the image should be much less troublesome
the jobs we had which built an ISO on every commit, but I'd like to=20
avoid overloading Jenkins as much as possible while still fulfilling
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
that it would be too invasive to trigger this new job on completion
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?
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
-----END PGP SIGNATURE-----