d set correct "defaults" for optional
> settings
This would mean that the jenkins plugins defaults would be overriden by
whatever jjb thinks is the default no? Would require to keep track of those
default values on the jjb side to match the versions of the plugins?
>
> Kien is my
hink that if you want to set defaults, you should do so in the default
construct instead, that also prevents that any change in the defaults on jjb
code from changing the generated xml.
> >
> > Thanh
> >
> > [1] https://review.openstack.org/261620/
> >
&
mmit
> messages (though there have been small incremental changes over time
> in the openstack-infra/jeepyb project, which should be detailed
> sufficiently in that project's commit history).
Thanks!!!
I'll take a look at the changes and see if the one that gerrit provides
