Loss of configuration after Jenkins restart

Using Jenkins Ask a question
1

Good afternoon,

We are modifying the security permissions in “Configure Global Security”, adding groups, removing users, etc, all using the “Project-based Matrix Authorization Strategy” authorisation option.

When we make modifications and Jenkins restarts, all the information of the configuration that has been modified is lost and the configuration that was there before remains.

We have solved this by updating Jenkins with the configuration file values.yaml. For example:

helm upgrade --wait --timeout 300s jenkins jenkins jenkinsci/jenkins --namespace jenkins --values 02b-jenkins-values.yaml

By doing this and then restarting Jenkins, the modifications persist and are not deleted.

Why does this happen?

Best regards,

Jorge.

2

There are several pieces of the puzzle missing in the description of your setup, but from the looks of it you are using JCasc to manage the configuration of your instance.

Jenkins will apply the JCasc configuration at startup and therefore override any manual configuration you did in the UI.

3

And I like it, because I know when i reboot jenkins it starts always with correct settings. :wink:

1 Like
4

Hi Jorge,

What values have you changed in jenkins-values.yaml file to persist “Project-based Matrix Authorization Strategy” data after restart of jenkins ?