Move jenkins auth settings to separate YAML #16
Conversation
With the jenkins auth config in the main jenkins.yaml, it's impossible to override this to use a different authentication method. Instead, move the auth into a seperate yaml file which can be overwritten/deleted by other deployments to use LDAP/github etc.
|
If this is accepted, it will presumably need a corresponding change in kernelci-jenkins-data, but I can't make that yet as haven't got my gpg key added to the repo. |
|
The files in the config directory aren't used anywhere on (staging.)kernelci.org, they are leftovers from the original setup which wasn't encrypted. In fact, they can't really be used as they are bound to be different for each Jenkins instance so can't be committed in git. So they are reference files, a starting point for someone setting up a new instance. It's a good idea anyway to improve them and if splitting the files helps with this then fine. |
|
Yes this keeps the reference working with local login with an admin password, but lets it be overridden for production use cases, without having to replace the whole jenkins.yaml file |
|
OK this is fine. The documentation should be updated now as the config seems to be stable. |
With the jenkins auth config in the main jenkins.yaml, it's impossible to override this to use a different authentication method.
Instead, move the auth into a seperate yaml file which can be overwritten/deleted by other deployments to use LDAP/github etc.