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

Select compatible plugin versions using a BOM

    XMLWordPrintable

Details

    Description

      Currently there is no easy way to use pipeline in unit tests.

      You need to add all of the required deps and exclude lots of conflicting versions of dependencies.

      It would be nice if I could just add a dependency on the aggregator with scope test and be done with it - but this also is not possible due to upper-bounds conflicts.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. JENKINS-51008 Complete the PCT flow started in JENKINS-50540 for git plugin

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • In Progress
          depends on

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-58716 Failure to check out specified tag for incremental version

          • Major - Major loss of function.
          • Resolved
          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-58615 incrementals:update ignores imported BOMs

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-33268 plugin-pom and core/war should produce/consume a BOM

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-48578 Create BOM for components included into the Core

          • Major - Major loss of function.
          • Resolved
          relates to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-49651 Extend plugin/update center metadata with known incompatibilities

          • Major - Major loss of function.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-45047 Easy way to run integration tests in plugin repositories

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • In Progress

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-58557 Separate @jenkinsci-specific archetype

          • Major - Major loss of function.
          • Resolved

          Task - A task that needs to be done. JENKINS-50953 Tool to offer incremental updates

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Task - A task that needs to be done. JENKINS-50540 add the runPCT step to the git-plugin on a PR basis

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          links to

          Web Link CloudBees Internal CJP-7862

          Web Link jenkinsci/bom repo

          Web Link pom-manipulation-ext

          Activity

            Ascending order - Click to sort in descending order
            jglick Jesse Glick added a comment -

            Add latest (baseline-compatible) versions of those plugins you are actually using in the test.

            Do not use exclusions. Just declare test-scoped dependencies on any otherwise transitive dependencies that requireUpperBoundDeps complains about.

            jglick Jesse Glick added a comment - Add latest (baseline-compatible) versions of those plugins you are actually using in the test. Do not use exclusions. Just declare test -scoped dependencies on any otherwise transitive dependencies that requireUpperBoundDeps complains about.
            jglick Jesse Glick added a comment -

            Converting to a more general RFE that the Jenkins project should publish a BOM somewhere you could import which specifies consistent versions of all plugins listed (incl. transitive dependencies) in the setup wizard’s suggested list; to be refreshed at least with every LTS line (versioned accordingly), and perhaps more often, taking latest versions from the update center.

            jglick Jesse Glick added a comment - Converting to a more general RFE that the Jenkins project should publish a BOM somewhere you could import which specifies consistent versions of all plugins listed (incl. transitive dependencies) in the setup wizard’s suggested list; to be refreshed at least with every LTS line (versioned accordingly), and perhaps more often, taking latest versions from the update center.
            jglick Jesse Glick added a comment -

            After getting some experience with the effect of a BOM on plugin POMs, I am becoming more convinced that this is the right direction. For example, common POM maintenance can be performed by adding entries to dependencyManagement, but just using a newer parent would be a lot simpler.

            jglick Jesse Glick added a comment - After getting some experience with the effect of a BOM on plugin POMs, I am becoming more convinced that this is the right direction. For example, common POM maintenance  can be performed by adding entries to dependencyManagement , but just using a newer parent would be a lot simpler.
            jglick Jesse Glick added a comment -

            rtyler suggest adding this to an Essentials sprint.

            jglick Jesse Glick added a comment - rtyler suggest adding this to an Essentials sprint.
            rtyler R. Tyler Croy added a comment -

            jglick, could you expand on why you're suggesting that? None of the work that I'm doing at the moment is around test infrastructure for plugins/core per se (ATH work excepted), and is mostly geared around delivering the Jenkins Essentials image.

            I can see a tenuous link here, but I'm not sure I fully understand why this suggests Jenkins Essentials prioritization right now
            ?

            rtyler R. Tyler Croy added a comment - jglick , could you expand on why you're suggesting that? None of the work that I'm doing at the moment is around test infrastructure for plugins/core per se (ATH work excepted), and is mostly geared around delivering the Jenkins Essentials image. I can see a tenuous link here, but I'm not sure I fully understand why this suggests Jenkins Essentials prioritization right now ?
            jglick Jesse Glick added a comment -

            Added to JENKINS-50686 since we might be able to use JENKINS-50953 to update the contents of the BOM.

            jglick Jesse Glick added a comment - Added to JENKINS-50686 since we might be able to use JENKINS-50953 to update the contents of the BOM.
            jglick Jesse Glick added a comment -

            Released a set of initial versions.

            jglick Jesse Glick added a comment - Released a set of initial versions.

            People

              jglick Jesse Glick
              teilo James Nord
              Votes:
              6 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: