-
Notifications
You must be signed in to change notification settings - Fork 236
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
update configuration-as-code #87
Comments
well, seems to have been tackled already by |
Hi @pniederlag You can change version of base plugins in Cheers |
Thx for your support! It seems the non semver version properties are somehow tricky, I had to quote them. Seems to work. If anyone needs to go that route, here is the patch on my jenkins_instance.yaml CRD |
Yes, e.g. 1.0 is interpreted as a float and 1.0.0 is interpreted as a
string, it's a YAML thing.
For the record, as suggested above, use quotes for non-semver versions,
e.g.: "1.0"
…On Tue, Sep 3, 2019 at 2:50 PM Peter Niederlag ***@***.***> wrote:
Thx for your support! It seems the non semver version properties are
somehow tricky, I had to quote them. Seems to work.
If anyone needs to go that route, here is the patch on my operator.yaml
0001-bugfix-add-all-basePlugins.txt
<https://github.com/jenkinsci/kubernetes-operator/files/3569472/0001-bugfix-add-all-basePlugins.txt>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#87?email_source=notifications&email_token=AAAL52VASOLJU4TEQYEIRB3QHZMSLA5CNFSM4ITEN522YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5YCQSY#issuecomment-527444043>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAL52S4SSKJBHZMKPDSBNTQHZMSLANCNFSM4ITEN52Q>
.
|
currently kubernetes-operator "ships" version 1.19 which has some known security-flaws: https://jenkins.io/security/advisory/2019-07-31/#SECURITY-1458
Please update the plugin (and it's companion configuration-as-code-support) to version 1.29
The text was updated successfully, but these errors were encountered: