Details
-
Type:
Task
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: blueocean-plugin
-
Labels:None
-
Similar Issues:
-
Epic Link:
-
Sprint:Blue Ocean 1.1
Description
Vivek, when running the ATH from the command line:
./run.sh -a=../blueocean/ -v=2.46.3
results in a failure to load plugins, due to it loading an older verison of the basic credentials or credentials binding plugins. This blue ocean won't work.
This may just be due to how the ATH loads things, vs a "real" update center and Jenkins, but I thought it may warrant a short investigation as to why this is a problem with newer jenkins.
To get this going I made this change: https://github.com/jenkinsci/blueocean-plugin/pull/1098 but I am not sure if that is "right" (it feels bad to put a direct dependency on something that should happily be transitive).
Is there something wrong with the blue ocean dpeendency graph causing this?
If it looks ok, close this as wont-fix, and instead we can add dependencies to the runtime-deps/pom.xml in the ATH dir instead (which won't touch the rest of bleu ocean).
Was uncovered by: https://issues.jenkins-ci.org/browse/JENKINS-39630 cc Ivan Meredith
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | JENKINS-36178 [ 172150 ] |
Rank | Ranked higher |
Status | Open [ 1 ] | In Progress [ 3 ] |
Resolution | Won't Fix [ 2 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Assignee | Vivek Pandey [ vivek ] | Ivan Meredith [ detab ] |
Resolution | Won't Fix [ 2 ] | |
Status | Closed [ 6 ] | Reopened [ 4 ] |
Assignee | Ivan Meredith [ detab ] | Ivan Meredith [ imeredith ] |
Status | Reopened [ 4 ] | In Progress [ 3 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Michael Neale Ivan Meredith, Spent some time on this. Looks like Jenkins 2.46.3 loads plugins differently than 2.7.3. Here is whats going on:
blueocean-pipeline-api-impl fails to load because plugins get loaded in this sequence:
If you look up at blueocean-pipeline-api-impl pom file, github-branch-source is before pipeline-model-definition and it gets resolved in that order, at least in 2.46.3. This results in jenkins loading github-branch-source first (which installed plain-credentials:1.1. and then it tries to install pipeline-model-definition and it fails because there is older version of plain-credentials(1.1) installed. See log: https://gist.github.com/vivek/54489c23c3cebe0eb7aa88aca1b4f920.
It might not just be issue of ATH, there are other use cases, like running aggregator inside another plugin. So, there are multiple-ways to fix it,
We should go for option 1 only if it breaks running aggregator as dependency in another plugin via mvn hpi:run. I will test it shortly. I would also like to test beta-5 (once we release it, shortly) on 2.46.3 to ensure all is well.