oVirt Node + VDSM Jenkins builder

[Ryan Barry]

Hey,

We on the Node team are planning on creating a Jenkins job to 
automatically add ovirt-node-plugin-vdsm to a base image in order to 
ease the burden of testing, and I'm looking for input from stakeholders 
on how we'd like to configure this.

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.

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.

Thoughts?