-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Upgrade kubernetes-client-api to 6.8.1 #1342
Upgrade kubernetes-client-api to 6.8.1 #1342
Conversation
For backward compatibility, converts decimal to octal notation
Remove usage of HttpClientUtils.getProxyUrl as it got removed in newer version of kubernetes-client
I notice that this plugin has a dependency on kubernetes-credentials-plugin. Do we need to make sure jenkinsci/kubernetes-credentials-plugin#39 is merged and released first, so we can use the release version for that in this plugin? |
It's probably safer. |
pom.xml
Outdated
<version>0.10.0</version> | ||
<!-- TODO https://github.com/jenkinsci/kubernetes-credentials-plugin/pull/39 @ f62dc9ee13617d84ec899274ed897668a4703242 --> | ||
<version>0.10.1-rc150.f62dc9ee1361</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pom.xml
Outdated
<!-- TODO https://github.com/jenkinsci/snakeyaml-api-plugin/pull/94 @ 4960f40749788fcfe6ddc7def8e0bbc0ce937046--> | ||
<version>2.1-110.v4960f4074978</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pom.xml
Outdated
<version>6.4.1-215.v2ed17097a_8e9</version> | ||
<version>6.8.1-220.v1f66736f9a_42</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jglick Any clue about this new warning raised in
Looks like it's called twice, and it seems like a normal condition? In that case it should be logged with level Stacktraces
vs. only one call in Stacktrace
Seems related to jenkinsci/workflow-durable-task-step-plugin#323, combined with https://github.com/jenkinsci/workflow-api-plugin/blob/2c63e4d244199a60ac7003c9b8813f36aad5f638/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowExecutionList.java#L83-L104 which has a side-effect of calling |
jenkinsci/workflow-api-plugin#304 seems to fix it |
Judging by the stack traces, it looks like a race condition: depending on timing, the |
As part of the snakeyaml (transitive) update a breaking change was introduced. The new I think it's worth noting in release notes @Vlatombe? |
Do you have a concrete use case for it ? I've never seen this operator being used in the context of this plugin |
Probably a general mention that snakeyaml-engine implements a new version of the yaml spec, and so anything that was relying on specifics of yaml 1.1 that got changed or removed in yaml 1.2 no longer works. |
Facing the same issues as https://issues.jenkins.io/browse/JENKINS-71956 Would there be a way to fix this in Thanks for any response! |
Downstream of jenkinsci/kubernetes-client-api-plugin#221
Breaking changes (from library):