System email address gets reset after restart
Closed this issue · 7 comments
Hello!
We have a Jenkins deployment running on Openshift and whenever the pod gets restarted, the System Admin e-mail address gets reset to the default nobody.
I identified /opt/openshift/configuration/jenkins.model.JenkinsLocationConfiguration.xml.tpl file as the template that is used on every startup. It is used to generate the location configuration file but only the Jenkins URL is substituted so the adminAddress field gets reset. I couldn't find a way to persist the email address after restarts. Could this be a bug or is there another way to keep the email address after restarts?
This is still an issue for us. Is there a chance this will be fixed?
@gaborfinta do you have the possibility to use the casc plugin to configure that?
The default casc config is in /var/lib/jenkins/proxy.yaml
We do not use that plugin.
Since the configuration file is a template file, it would be the best to substitute all values in it. For example, the email address would get its value from a "JENKINS_EMAIL" environment variable.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.