Manage jenkins global config and plugin list
Bug #1082803 reported by
Monty Taylor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Core Infrastructure |
Fix Released
|
Medium
|
Khai Do |
Bug Description
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.
Changed in openstack-ci: | |
milestone: | grizzly → havana |
Changed in openstack-ci: | |
assignee: | nobody → Khai Do (zaro0508) |
Changed in openstack-ci: | |
status: | Triaged → In Progress |
To post a comment you must log in.
For the sack of tracability:
- Add jenkins::plugin defined resource type /review. openstack. org/#/c/ 39615/
https:/
- Don't automatically restart jenkins on plugin changes /review. openstack. org/#/c/ 40040/
https:/
- Add current jenkins plugins /review. openstack. org/#/c/ 40041/
https:/