-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
CASC: 1.23
Jenkins 2.176.2
Jenkins startup fails if the yaml file contains unknown entries.
This happens when uninstalling a plugin like the old warnings plugin.
This had a section globalSettings in the casc yaml file which was not removed. After uninstalling the plugin, jenkins could not start anymore because casc failed.
It would be much better if the casc plugin would warn about unknown entries and skip them instead to fail completely.
This also happens when using an invalid url like a raw GitHub url with temporary token. If a user has an invalid url to a file the master fails to startup since it no longer has access to the file.
Seen in Jenkins 2.235.3
[id=27] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed ConfigurationAsCode.init
java.io.FileNotFoundException:
+1 on the plugin needs to not fail startup based on bad static configuration entries by a user. Steps to remedy were to update the io.jenkins.plugins.casc.CasCGlobalConfig.xml and remove the bad <configurationPath></configurationPath>
I have filed https://github.com/jenkinsci/configuration-as-code-plugin/issues/1449 and will attempt to make some progress on a fix if ewel doesn't get to it first