-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for separators broke existing CasC configuration #159
Comments
I need unit tests |
Marked the release as breaking CasC for now |
I see the warning at https://github.com/jenkinsci/customizable-header-plugin/releases/tag/141.vdd3dcb_cfcf66 but not yet at https://plugins.jenkins.io/customizable-header/releases/#version_141.vdd3dcb_cfcf66. I wonder how soon it will propagate there. 13:03 UTC: The warning has propagated. |
Same issue here after upgrade. I will apply the JCasC change |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Windows
Reproduction steps
I had configured the customizable header in
jenkins.yaml
with this kind of structure:and then upgraded customizable-header-plugin from 140.v8e771d054075 to 141.vdd3dcb_cfcf66.
Expected Results
Jenkins should start OK with the existing
jenkins.yaml
, or alternatively, the customizable-header 141.vdd3dcb_cfcf66 release notes should warn that it is not compatible.Actual Results
Jenkins did not start:
Anything else?
Presumably caused by #158.
Looks like
jenkins.yaml
has to be restructured like this in 141.vdd3dcb_cfcf66:Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: