Skip to content

update workflow-api version 2.40 #119

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

Merged
merged 3 commits into from
Feb 24, 2020

Conversation

joseblas
Copy link
Contributor

@joseblas joseblas commented Feb 20, 2020

This update is needed for PCT issues

@joseblas joseblas changed the title bumping ssh-slaves version for Jenkins 2.204 [WIP] bumping ssh-slaves version for Jenkins 2.204 Feb 20, 2020
@joseblas joseblas changed the title [WIP] bumping ssh-slaves version for Jenkins 2.204 bumping ssh-slaves version for Jenkins 2.204 Feb 20, 2020
@joseblas joseblas requested a review from jglick February 20, 2020 18:09
@joseblas joseblas changed the title bumping ssh-slaves version for Jenkins 2.204 update workflow-api version 2.40 Feb 20, 2020
Copy link
Member

@dwnusbaum dwnusbaum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fine, but do you have any context? Is this because of a plugin split or something in core? Are you trying to fix PCT issues, etc? It is very helpful to link to any relevant upstream PRs so that anyone looking through in the future can figure out why this was needed, and so anyone looking at the upstream PR can see what plugins were forced to adapt because of the change, etc.

Co-Authored-By: Devin Nusbaum <[email protected]>
Copy link
Member

@jglick jglick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no context given. Maybe the PR title could say something about adapting to new ssh-slaves releases or something?

@@ -150,7 +150,7 @@
<dependency>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>ssh-slaves</artifactId>
<version>1.26</version>
<version>1.30.1</version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you use the BOM instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you mean to add a bom to the ssh-slaves plugin?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, to use jenkinsci/bom here rather than hard-coding individual plugin versions. Not necessary and could be done as a follow-up of course.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, I will do it in another branch. Thanks

@dwnusbaum
Copy link
Member

dwnusbaum commented Feb 24, 2020

Ok, I tried to track down the reason for the change. My best guess is that it is because jenkinsci/ssh-agents-plugin#114, released in ssh-slaves 1.30.0, broke binary compatibility by removing deprecated methods on SSHLauncher which we were using in tests, and because that PR updated the Jenkins core dependency to a newer version than this plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants