Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

[JENKINS-39414] - Update Stapler JRuby dependency to prevent binary compat issue in Jenkins 2.28+ #4

Conversation

oleg-nenashev
Copy link
Member

Stapler 1.246 introduced new APIs, and unfortunately this APIs do not work correctly with outdated modules of stapler like Stapler JRuby. It caused a blocker regression for updating users (see JENKINS-39414).

Fix/hack on the stapler side: jenkinsci/stapler#85

@reviewbybees @jenkinsci/code-reviewers

@rtyler
Copy link
Member

rtyler commented Nov 2, 2016

Build timeout, weak 😦

@ghost
Copy link

ghost commented Nov 2, 2016

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@oleg-nenashev
Copy link
Member Author

Increased timeout

@@ -15,7 +15,7 @@
<dependency>
<groupId>org.kohsuke.stapler</groupId>
<artifactId>stapler-jruby</artifactId>
<version>1.229</version>
<version>1.246</version>
Copy link
Member

@rsandell rsandell Nov 2, 2016

Choose a reason for hiding this comment

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

would this work when running on an older Jenkins core with older stapler?

Copy link
Member Author

Choose a reason for hiding this comment

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

At least it works on my small test instance

@rsandell
Copy link
Member

rsandell commented Nov 2, 2016

🐝

@oleg-nenashev
Copy link
Member Author

the build hangs somewhere

@michaelneale
Copy link
Member

🐝 not sure about the build

@oleg-nenashev
Copy link
Member Author

IMHO this fix requires plenty of compatibility testing on older versions. My advice is to go forward with jenkinsci/stapler#85 and leave this guy for a while

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.

🐝

@daniel-beck
Copy link
Member

@oleg-nenashev Are we sure this is the correct repo, and not this?

@oleg-nenashev
Copy link
Member Author

Yes, wrong repo. Should be tombstoned or even deleted

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

Successfully merging this pull request may close these issues.

6 participants