Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44533

Investigate changes in plugin loading with LTS vs 2.7.3 that cause failures in ATH

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • blueocean-plugin
    • None
    • Blue Ocean 1.1

      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 imeredith

            imeredith Ivan Meredith
            michaelneale Michael Neale
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: