I'd like Jenkins to reload its configuration from disk when receiving a signal like SIGHUP. That way Jenkins' configuration can be managed with e.g. jenkins-job-builder (or any configuration management system) without having to setup users and auth for the Web UI.
Currently I use a big hammer and restart Jenkins when I have some configuration changes to deploy. This is not a good solution because it aborts all running jobs.
Actually, it doesn't have to be a signal. Any mechanism that relies only on local users would be fine. Like extending the Jenkins CLI to work over UNIX sockets. (System admin can limit access to the UNIX socket so that only privileged users can connect.)
Similar question asked here: