| We are running a Jenkins server that hosts a number of legacy builds using statically managed build nodes, as well as an increasing amount of builds running on Kubernetes agents. Both flavors use Jenkinsfiles with declarative pipelines. Right now, this results in a bunch of configurations maintained twice: Once for the legacy builds using Jenkins' Managed Files and Credentials (e.g. Maven settings.xml and Nexus credentials). And once more through manually created ConfigMaps and Secrets for the K8S builds. It would be great if the Kubernetes Plugin could be configured to automatically create ConfigMaps and Secrets in the cluster for all (or a selected subset of) managed files and credentials and keep them uptodate if they change in the Jenkins config. |
