Manage jenkins global config and plugin list

[Monty Taylor]

In a future utopia where we spin up new jenkins masters as part of a pool, the global config and the plugins to be installed need to be managed in some sane manner. At the moment, this would mean in our puppet modules. If the tripleo team gets a repeatable jenkins image working, then perhaps it goes in part of the image creation pipeline. In any case, we need it to be somewhere before we can have multiple jenkins masters running around.

[Mathieu Gagné (mgagne)]

For the sack of tracability:

- Add jenkins::plugin defined resource type
https://review.openstack.org/#/c/39615/

- Don't automatically restart jenkins on plugin changes
https://review.openstack.org/#/c/40040/

- Add current jenkins plugins
https://review.openstack.org/#/c/40041/

[Khai Do (zaro0508)]

The plugin bits have been handled. Solving management for the global config is still an open issue.

[Khai Do (zaro0508)]

Created upstream bug for de-coupling configurations in jenkins global config.xml: https://issues.jenkins-ci.org/browse/JENKINS-21006

[Khai Do (zaro0508)]

It seems that we are able to manage this in puppet.
http://git.openstack.org/cgit/openstack-infra/config/tree/modules/jenkins/manifests/plugin.pp
http://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/manifests/jenkins.pp#n57

I will close out this issue.