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

Create BOM for components included into the Core

    XMLWordPrintable

Details

    • New Feature
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • bom, core
    • None

    Description

      The idea of this BOM is to simplify the dependency management in plugins and modules.

      Proposed changes:

      1. New BOM module in the jenkinsci/jenkins repository. We could have an external BOM, but it complicates the release management
      2. Move library definitions from Parent POM and Jenkins WAR to the BOM file
      3. Update WAR and Core components to use BOM
      4. Update plugin POM to optionally include BOM if possible (depending on jenkins.version)

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-47498 Select compatible plugin versions using a BOM

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

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-49565 Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core

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

          Web Link core PR

          Web Link plugin-pom PR

          Activity

            Ascending order - Click to sort in descending order
            View 12 older comments
            teilo James Nord added a comment -

            >  Even if there is a consensus to backport it, it is likely to be 2.190.2 only

            If it prevents the "oh shit I forgot to push a release of the bom after a release was made" that's a win in my eyes.  We're aware the .1 boat has sailed and we where a little late to merge the original bom and hence make the backport request.

            teilo James Nord added a comment - >  Even if there is a consensus to backport it, it is likely to be 2.190.2 only If it prevents the "oh shit I forgot to push a release of the bom after a release was made" that's a win in my eyes.  We're aware the .1 boat has sailed and we where a little late to merge the original bom and hence make the backport request.
            danielbeck Daniel Beck added a comment -

            Why is this issue still open?

            danielbeck Daniel Beck added a comment - Why is this issue still open?
            oleg_nenashev Oleg Nenashev added a comment -

            I think all proposed changes are delivered. All minor follow-ups can be handled separately

            oleg_nenashev Oleg Nenashev added a comment - I think all proposed changes are delivered. All minor follow-ups can be handled separately
            markwm Mark Wynn-Mackenzie added a comment -

            Yes, they are. Sorry, it just got missed.

            markwm Mark Wynn-Mackenzie added a comment - Yes, they are. Sorry, it just got missed.
            danielbeck Daniel Beck added a comment -

            teilo If you label an issue lts-candidate, you should make sure its issue type doesn't disqualify it from backporting: https://issues.jenkins-ci.org/issues/?filter=12146

            danielbeck Daniel Beck added a comment - teilo If you label an issue lts-candidate, you should make sure its issue type doesn't disqualify it from backporting: https://issues.jenkins-ci.org/issues/?filter=12146

            People

              markwm Mark Wynn-Mackenzie
              oleg_nenashev Oleg Nenashev
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: