Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins reload #10

Open
ip1981 opened this issue May 18, 2017 · 0 comments
Open

Jenkins reload #10

ip1981 opened this issue May 18, 2017 · 0 comments

Comments

@ip1981
Copy link
Owner

ip1981 commented May 18, 2017

Objective: make Jenkins able to deploy itself. This requires graceful shutdown after all jobs are done. Then systemd will start Jenkins again, probably new version of it.

Jenkins may expose unprotected URL endpoint to trigger shutdown. This is to be used by automated scripts in Jenkins app itself. "Unprotected" means that the URL or credentials (or maybe UNIX socket) is only known to Jenkins user.

Possible implementation:

  1. "backdoor" plugin injected on each deploy in addition to any other plugins.
  2. This plugin exposes the endpoint URL like /<secret>/shutdown. The <secret> is new on each start and is written to a private file.
  3. When configuration is changed, a script reads the secret file, finds the URL and hits it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant