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

Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages

    • Evergreen - Milestone 1

      Issue

      We get a bunch of WARNINGs back to Sentry backend for Evergreen.

      Typical message:

      Created /evergreen/jenkins/var/plugins/authentication-tokens/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
      // or
      Created /evergreen/jenkins/var/plugins/conditional-buildstep/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
      ...
      

      Expected

      We should probably make a pass to either update to last versions that might already be fixed, or propose patches around to have this cleaned up.

      list of plugins suffering from this visible through Sentry

      • authentication-tokens
      • conditional-buildstep
      • icon-shim
      • javadoc
      • jsch
      • mapdb-api
      • maven-plugin
      • node-iterator-api
      • run-condition

          [JENKINS-53285] Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages

          Baptiste Mathus created issue -
          Baptiste Mathus made changes -
          Sprint New: Evergreen - Milestone 1 [ 511 ]
          Baptiste Mathus made changes -
          Description Original: h3. Issue

          We get a bunch of WARNINGs back to Sentry backend for Evergreen.

          Typical message:

          {noformat}
          Created /evergreen/jenkins/var/plugins/authentication-tokens/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
          // or
          Created /evergreen/jenkins/var/plugins/conditional-buildstep/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
          ...
          {noformat}

          We should probably make a pass to either update to last versions that might already be fixed, or propose patches around to have this cleaned up.
          New: h3. Issue

          We get a bunch of WARNINGs back to Sentry backend for Evergreen.

          Typical message:

          {noformat}
          Created /evergreen/jenkins/var/plugins/authentication-tokens/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
          // or
          Created /evergreen/jenkins/var/plugins/conditional-buildstep/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
          ...
          {noformat}

          h3. Expected

          We should probably make a pass to either update to last versions that might already be fixed, or propose patches around to have this cleaned up.

          h3. list of plugins visible through Sentry
          Baptiste Mathus made changes -
          Labels Original: evergreen-triggered New: evergreen evergreen-triggered sentry
          Baptiste Mathus made changes -
          Description Original: h3. Issue

          We get a bunch of WARNINGs back to Sentry backend for Evergreen.

          Typical message:

          {noformat}
          Created /evergreen/jenkins/var/plugins/authentication-tokens/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
          // or
          Created /evergreen/jenkins/var/plugins/conditional-buildstep/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
          ...
          {noformat}

          h3. Expected

          We should probably make a pass to either update to last versions that might already be fixed, or propose patches around to have this cleaned up.

          h3. list of plugins visible through Sentry
          New: h3. Issue

          We get a bunch of WARNINGs back to Sentry backend for Evergreen.

          Typical message:

          {noformat}
          Created /evergreen/jenkins/var/plugins/authentication-tokens/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
          // or
          Created /evergreen/jenkins/var/plugins/conditional-buildstep/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
          ...
          {noformat}

          h3. Expected

          We should probably make a pass to either update to last versions that might already be fixed, or propose patches around to have this cleaned up.

          h3. list of plugins suffering from this visible through Sentry

          * authentication-tokens
          * conditional-buildstep
          * icon-shim
          * javadoc
          * jsch
          * mapdb-api
          * maven-plugin
          * node-iterator-api
          * run-condition
          Baptiste Mathus made changes -
          Link New: This issue relates to JENKINS-53251 [ JENKINS-53251 ]

          Jesse Glick added a comment -

          The maven-plugin version currently being bundled is close to five years old, FYI. Need to fix this or the project will get nicknamed Deciduous!

          Jesse Glick added a comment - The maven-plugin version currently being bundled is close to five years old, FYI. Need to fix this or the project will get nicknamed Deciduous!

          I'm doing a quick pass to update at least things that are already fixed like this case of the maven-plugin (even if we filter its descriptors out, but well ). For things that will need code fixing, I think we'll plan differently and see how/when/if to do it.

          Baptiste Mathus added a comment - I'm doing a quick pass to update at least things that are already fixed like this case of the maven-plugin (even if we filter its descriptors out, but well ). For things that will need code fixing, I think we'll plan differently and see how/when/if to do it.

          Jesse Glick added a comment -

          Right. The “code fixes” should in general simply be using a newer parent POM, to pick up a newer maven-hpi-plugin. I think we would expect that all plugins bundled in Evergreen ought to be using recent parents, for various reasons.

          Jesse Glick added a comment - Right. The “code fixes” should in general simply be using a newer parent POM, to pick up a newer maven-hpi-plugin . I think we would expect that all plugins bundled in Evergreen ought to be using recent parents, for various reasons.
          R. Tyler Croy made changes -
          Issue Type Original: Epic [ 10001 ] New: Bug [ 1 ]

            batmat Baptiste Mathus
            batmat Baptiste Mathus
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: