Open v1v opened 9 years ago
@v1v for the record, I use the feedback-needed
label when I need feedback from the original submitter of an issue. This got overlooked because I assumed it was waiting for somebody to add more details in :)
Anyways, I think the idea is a reasonable one but the number of ways a process might be configured to prevent CLI access concerns me. We'll need to make the script much more bullet-proof I think to where if it cannot access the Jenkins service for whatever reason it falls back to the raw process kill/restart semantics
It shouldn't be to difficult to implement a service provider that uses the cli to invoke safe-restart.
Use case: if any changes then restart jenkins but bear in mind if you restart it might stop/abort those builds which are still running.
Current configuration:
File: manifests/services.pp
Suggested configuration:
File: manifests/services.pp
File: templates//jenkins-safe-restart.erb
Downsides:
It works as long your Administration security is not in place or you already configured with some granted privileges... or added some cli login setup via -i flag "-i ~jenkins/.ssh/jenkins_id_rsa" or so
In fact: jenkins::cli::safe-restart command might not work if those security layouts are in place AFAIK
Further details: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI (Working with Credentials section).
Let me know your thoughts
Cheers