On Tue, 2018-04-17 at 11:19 +0100, Daniel P. Berrangé wrote:
On Tue, Apr 17, 2018 at 12:13:01PM +0200, Andrea Bolognani wrote:
> Do you want me to send v2, or can I just squash this in and push?
Fine to squash it unless you notice something complicated needs
furtehr changing.
Hm, Jenkins Job Builder is actually not happy with that:
ERROR:jenkins_jobs.parser:Duplicate definitions for
job 'libvirt-master-build' specified
which makes sense because generic-build-jobs has
name: '{name}-{branch}-build'
I could trick it into using a different name with
- generic-build-job:
name: libvirt-website
...
but then it would try to fetch new revisions from
git://n64.pufty.ci.centos.org/libvirt-website.git
which of course doesn't exist...
Given the situation, my original approach might be the best
solution to the problem after all. What's your take?
--
Andrea Bolognani / Red Hat / Virtualization