We patched the upstream puppet-jenkins module to have a better service definition working with Debian's Jenkins daemon.
feature/better_service_definition branch of the Tails puppet-jenkins module clone.
But our puppet-module is lagging a lot behind the upstream.
We need to first upgrade this module and check if this change is still relevant. If it is, then we'll have to upstream it.
#5 Updated by bertagaz about 4 years ago
This ticket is a duplicate of the buggy #9618, means to replace it.
Yes, but I actually can't close it (the status are limited), and its notes contains informations. I'm a bit afraid of losing it if I manipulate it, so I prefer to wait for this new ticket to be closed to take care of #9618.
#8 Updated by bertagaz about 4 years ago
- % Done changed from 0 to 90
- QA Check changed from Info Needed to Ready for QA
So, I've updated the jenkins module to last upstream tag + our stronger_plugin_verification branch, and the service seems to be managed correctly by default by the upstream manifests. I've just dropped that patch from our module.
I don't think we need to upstream this old change anymore. Delta--, yay!
#9 Updated by intrigeri about 4 years ago
But I can't close #9619 (really), gives me "Invalid parent" when I try, and I can't change its parent, gives me a 404...
parent_id was set to 6956, which I mistakenly deleted (still don't know how, but well). I've fixed that in the database, and could then close #9619 and #9618 :) Sorry for creating this mess...
#11 Updated by intrigeri about 4 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
- QA Check changed from Ready for QA to Pass
So, I've updated the jenkins module to last upstream tag + our stronger_plugin_verification branch, and the service seems to be managed correctly by default by the upstream manifests.
- by manually stopping the service: Puppet correctly restarts it
- Puppet doesn't restart the service if already running.