hi
On 18/04/15 14:58, Colin Walters wrote:
As the next step, I'd like to now expand this to run a build for every git branch in the upstream sig-atomic-buildscripts repo. What / how should we handle naming those ?
One thing that Ari and I have been exploring is using Jenkins for these sort of "post-Koji" tasks as it has a wealth of plugins (messaging, irc notification etc.), and supports "parameterization" of jobs which is is exactly what you mentioned above.
We might take the short route and add something to the mash runs for the time being, longer term getting a plugin that can mark a build as fail, when a test fails would be good.
I'll see if we can get the prototype published soon, it's using jenkins-job-builder (which btw is now packaged for Fedora https://bugzilla.redhat.com/show_bug.cgi?id=1208904 and should be easily built on C7)
This is sort of where I started from initially, having the work just get done and triggered from a jenkins job, Lets see how it works for the that model, we can always just go to this anytime. When we looked at JJB, it seemed limited in what plugins and what things it might be able to do, but its worth a revisit if it helps solve these issues.