Missing plugins configuration

[Javier Collado]

When jobs are generated using setup-jobs.py, I see there are some sections in
the current jobs that isn't available in the same jobs when generated using the
script.

In particular, xml isn't generated for the BuildPublisher plugin:
> <hudson.plugins.build__publisher.BuildPublisher>
> <publishUnstableBuilds>true</publishUnstableBuilds>
> <publishFailedBuilds>true</publishFailedBuilds>
> <postActions class="vector"/>
> </hudson.plugins.build__publisher.BuildPublisher>

and for the DescriptionSetterPublisher plugin:
> <hudson.plugins.descriptionsetter.DescriptionSetterPublisher>
> <regexp>Media Info:.* \(([\d.]+)\)</regexp>
> <regexpForFailed>Media Info:.* \(([\d.]+)\)</regexpForFailed>
> <description>\1</description>
> <descriptionForFailed>\1</descriptionForFailed>
> <setForMatrix>false</setForMatrix>
> </hudson.plugins.descriptionsetter.DescriptionSetterPublisher>

In addition to this, there's a buildWrappers section that is empty when the job
is generated using the script, but it seems to be like this in the current jobs:
> <buildWrappers>
> <EnvInjectBuildWrapper>
> <info>
> <loadFilesFromMaster>false</loadFilesFromMaster>
> </info>
> </EnvInjectBuildWrapper>
> </buildWrappers>

It should be possible to have all this in the jobs when they're generated using
the script, so that manual work isn't needed when updating the jobs using the
script.

Regarding publishing results, a boolean command line option could be added to
decide if results should be published or not (interesting when the job is new
and needs some testing first).

[Max Brustkern (nuclearbob)]

This affects the job setup script in the utah-bootspeed branch as well.

[Javier Collado (javier.collado)]

The build publisher part is in place, but it seems that the plugin isn't
available in the local instance I'm using for testing and that part is removed
when the configuration is updated.

[Javier Collado (javier.collado)]

In fact this happens for the other parts in the bug description as well, so
maybe this bug is Invalid. I'm going to use the staging jenkins instance that
has the same configuration to make sure.

[Javier Collado (javier.collado)]

Finally it seems it was just my mistake when verifying the generated xml in a
different environment. I guess this applies to the bootspeed script, but I'm
just marking as Invalid the part of this bug related to smoke testing.

[Max Brustkern (nuclearbob)]

Is this still an issue, or have we fixed it already?

[Javier Collado (javier.collado)]

Yes, the real problem was that the configuration for some plugin is dropped if
the target jenkins instance doesn't have that plugin installed. That confused
me and I though it was a problem in the templates, but it wasn't.

With regard to the part that is still open about bootspeed, I haven't checked
the code, but probably isn't an issue.

[Max Brustkern (nuclearbob)]

We've got publishing in the templates for bootspeed at this point, so I think one should be in good shape.