Re: [libvirt] [jenkins-ci PATCH v2 3/6] projects: Add libvirt-master-website job

On Tue, 2018-04-17 at 13:08 +0100, Daniel P. Berrangé wrote: > Hmm, this is a problem with us repurposing 'name' as a parameter > for the template, when it is also a declared field. > > eg the core issue is this: > > name: '{name}-{branch}-build' > > We should address this by changing the parameter name to be > 'projname', so it doesn't clash with the official 'name' > field used as the job name. Are you sure? It seems to me like the problem stems from the fact that we have both - job-template: id: autotools-build-job name: '{name}-{branch}-build' and - job-template: id: generic-build-job name: '{name}-{branch}-build' Even if we had a separate 'projname' parameter, the names of the generated jobs would end up being the same.