Details
-
Task
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
-
2.14.4
Description
as per https://github.com/jenkinsci/subversion-plugin/pull/254#issuecomment-858288074 reported by basil
There looks like there is a regression (in waiting?) in the Subversion plugin against Pipeline and Jenkins core. (and potentially the other plugins in which Digester2 was removed.
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Summary | Subversion / pipeline ASM compatability issue | Analyze / fix Subversion / pipeline ASM compatibility issue |
Assignee | James Nord [ teilo ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | James Nord [ teilo ] | Foundation Team [ foundation_test_security_members ] |
Assignee | Foundation Team [ foundation_test_security_members ] | Carroll Chiou [ carroll ] |
Issue Type | Bug [ 1 ] | Task [ 3 ] |
Comment | [ I've changed the type from Bug to Task as it seems there is no real regression in the production environment, but in test one. ] |
Remote Link | This issue links to "jenkinsci/subversion-plugin#257 (Web Link)" [ 26780 ] |
Remote Link | This issue links to "https://github.com/jenkinsci/subversion-plugin/pull/259 (Web Link)" [ 26785 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Fixed but Unreleased [ 10203 ] |
Released As | 2.14.4 | |
Status | Fixed but Unreleased [ 10203 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Released As | 2.14.4 | 2.14 |
Resolution | Fixed [ 1 ] | |
Status | Reopened [ 4 ] | Fixed but Unreleased [ 10203 ] |
Released As | 2.14 | 2.13 |
Status | Fixed but Unreleased [ 10203 ] | Resolved [ 5 ] |
Released As | 2.13 | 2.14.4 |
Since the problematic frames in the stack trace originate with Stapler, the impact of the regression should be limited to JenkinsRule-based tests only, not production (based on the reasoning James and I agreed on in the mailing list thread). Several of the Pipeline plugins depend on Subversion in their tests, though, and the BOM runs PCT on those Pipeline plugins, so we need to find some way to get these tests working again before we start a new BOM line for the LTS release after 2.289.