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

Jenkins 2.361 core sources & javadoc not on repo.jenkins-ci.org

    • 2.362

      The jar files for Jenkins 2.361 sources and javadoc are not available on repo.jenkins-ci.org while the jar files for Jenkins 2.360 sources and javadoc are available on repo.jenkins-ci.org.

      As a possible cause, I see that the Jenkins weekly release 2.361 has changed from maven deploy plugin 2.8.2 to 3.0.0. That upgrade may have changed the uploaded artifacts that are published by the Jenkins weekly build.

      The 2.360 war deploy fragment of the build log looks like this:

      [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ jenkins-war ---
      [INFO] Using alternate deployment repository releases::default::https://repo.jenkins-ci.org/releases
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.war
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.war (93 MB at 25 MB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.pom
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.pom (6.7 kB at 41 kB/s)
      [INFO] Downloading from releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/maven-metadata.xml
      [INFO] Downloaded from releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/maven-metadata.xml (25 kB at 335 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/maven-metadata.xml
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/maven-metadata.xml (25 kB at 139 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.license.xml
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.license.xml (36 kB at 208 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.license.html
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.license.html (31 kB at 179 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360-sources.jar
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360-sources.jar (68 kB at 401 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360-javadoc.jar
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360-javadoc.jar (402 kB at 2.0 MB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.war.asc
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.war.asc (833 B at 12 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.pom.asc
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.pom.asc (833 B at 11 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.license.xml.asc
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.license.xml.asc (833 B at 12 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.license.html.asc
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360.license.html.asc (833 B at 12 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360-sources.jar.asc
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360-sources.jar.asc (833 B at 12 kB/s)
      [INFO] Uploading to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360-javadoc.jar.asc
      [INFO] Uploaded to releases: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/jenkins-war-2.360-javadoc.jar.asc (833 B at 11 kB/s)
      

      The 2.361 war deploy fragment of the build log looks like this:

      [INFO] --- maven-deploy-plugin:3.0.0:deploy (default-deploy) @ jenkins-war ---
      [INFO] Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.pom
      [INFO] Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.pom (6.7 kB at 17 kB/s)
      [INFO] Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.war
      [INFO] Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.war (93 MB at 27 MB/s)
      [INFO] Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.license.xml
      [INFO] Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.license.xml (36 kB at 201 kB/s)
      [INFO] Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.license.html
      [INFO] Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.license.html (31 kB at 188 kB/s)
      [INFO] Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.war.asc
      [INFO] Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.war.asc (833 B at 13 kB/s)
      [INFO] Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.pom.asc
      [INFO] Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.pom.asc (833 B at 13 kB/s)
      [INFO] Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.license.xml.asc
      [INFO] Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.license.xml.asc (833 B at 12 kB/s)
      [INFO] Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.license.html.asc
      [INFO] Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/jenkins-war-2.361.license.html.asc (833 B at 13 kB/s)
      [INFO] Downloading from maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/maven-metadata.xml
      [INFO] Downloaded from maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/maven-metadata.xml (25 kB at 365 kB/s)
      [INFO] Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/maven-metadata.xml
      [INFO] Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/maven-metadata.xml (25 kB at 166 kB/s)
      

      As a result, the sources and javadoc for the Jenkins weekly release 2.361 are not available on https://repo.jenkins-ci.org . Compare the contents of https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-core/2.360/ and https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-core/2.361/ to see the difference.

      The backend extension indexer job that generates the list of extensions is unable to find the source code for Jenkins core 2.361 and fails its CI job.

      Actual results

      Contents of https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.361/

      jenkins-war-2.361.license.html       26-Jul-2022 12:49  30.33 KB
      jenkins-war-2.361.license.html.asc   26-Jul-2022 12:49  833 bytes
      jenkins-war-2.361.license.xml        26-Jul-2022 12:49  35.56 KB
      jenkins-war-2.361.license.xml.asc    26-Jul-2022 12:49  833 bytes
      jenkins-war-2.361.pom                26-Jul-2022 12:49  6.54 KB
      jenkins-war-2.361.pom.asc            26-Jul-2022 12:49  833 bytes
      jenkins-war-2.361.war                26-Jul-2022 12:49  89.12 MB
      jenkins-war-2.361.war.asc            26-Jul-2022 12:49  833 bytes
      

      Expected results

      Contents of https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/2.360/ (notice the javadoc and sources jar files)

      jenkins-war-2.360-javadoc.jar        19-Jul-2022 12:43  392.64 KB
      jenkins-war-2.360-javadoc.jar.asc    19-Jul-2022 12:43  833 bytes
      jenkins-war-2.360-sources.jar        19-Jul-2022 12:43  66.57 KB
      jenkins-war-2.360-sources.jar.asc    19-Jul-2022 12:43  833 bytes
      jenkins-war-2.360.license.html       19-Jul-2022 12:43  30.33 KB
      jenkins-war-2.360.license.html.asc   19-Jul-2022 12:43  833 bytes
      jenkins-war-2.360.license.xml        19-Jul-2022 12:43  35.56 KB
      jenkins-war-2.360.license.xml.asc    19-Jul-2022 12:43  833 bytes
      jenkins-war-2.360.pom                19-Jul-2022 12:43  6.54 KB
      jenkins-war-2.360.pom.asc            19-Jul-2022 12:43  833 bytes
      jenkins-war-2.360.war                19-Jul-2022 12:43  89.10 MB
      jenkins-war-2.360.war.asc            19-Jul-2022 12:43  833 bytes
      

          [JENKINS-69198] Jenkins 2.361 core sources & javadoc not on repo.jenkins-ci.org

          Basil Crow added a comment -

          I don't know the answer and it would probably take me longer to figure it out and explain it than to figure it out and implement a fix.

          Basil Crow added a comment - I don't know the answer and it would probably take me longer to figure it out and explain it than to figure it out and implement a fix.

          Basil Crow added a comment -

          Caused by …

          … both of which failed to follow the migration instructions documented in Migrate Maven Release Plugin From 2 to 3:

          Context: Maven 3 and Maven 4

          Maven 3 (and previously 2) provides a default release profile named release-profile that builds and attaches source and javadoc jar: this is defined in the super POM. This profile is activated by default during release:perform with Maven Release Plugin 2.x, unless deactivated by configuring useReleaseProfile parameter to false.

          In Maven 4, this default profile will be removed from super POM (see MNG-7029).

          To prepare for this removal, Maven Release Plugin 3.0 stopped invoking this profile by default: useReleaseProfile parameter is false by default.

          Upgrading Maven Release Plugin 2 to 3

          Write And Configure Your Own Release Profile

          In order to prepare for Maven 4, each project will instead require to define their own release profile that they'll be able to customise to match their needs:

          • for internal projects, just configure the maven-source-plugin for example
          • for projects published to Maven Central repository, you'll need to add also maven-javadoc-plugin and maven-gpg-plugin: see the documentation.
            Notice: if you already published to Maven Central, there is a good chance the configuration has already been done in a parent POM.

          Then configure maven-release-plugin to use that profile during release:perform with releaseProfiles parameter […]

          Short Term: Force Using Maven 3-only Default Release Profile

          Configuring explicitely useReleaseProfile parameter to true will force Maven Release Plugin 3 to work like version 2.

          It provides an easy but temporary solution, working only with Maven 3, when you can't yet write your own release profile.

          Basil Crow added a comment - Caused by … https://github.com/jenkinsci/plugin-pom/pull/558 https://github.com/jenkinsci/pom/pull/281 … both of which failed to follow the migration instructions documented in Migrate Maven Release Plugin From 2 to 3 : Context: Maven 3 and Maven 4 Maven 3 (and previously 2) provides a default release profile named release-profile that builds and attaches source and javadoc jar: this is defined in the super POM . This profile is activated by default during release:perform with Maven Release Plugin 2.x, unless deactivated by configuring useReleaseProfile parameter to false . In Maven 4, this default profile will be removed from super POM (see MNG-7029 ). To prepare for this removal, Maven Release Plugin 3.0 stopped invoking this profile by default: useReleaseProfile parameter is false by default. Upgrading Maven Release Plugin 2 to 3 Write And Configure Your Own Release Profile In order to prepare for Maven 4, each project will instead require to define their own release profile that they'll be able to customise to match their needs: for internal projects, just configure the maven-source-plugin for example for projects published to Maven Central repository , you'll need to add also maven-javadoc-plugin and maven-gpg-plugin : see the documentation . Notice: if you already published to Maven Central, there is a good chance the configuration has already been done in a parent POM. Then configure maven-release-plugin to use that profile during release:perform with releaseProfiles parameter […] Short Term: Force Using Maven 3-only Default Release Profile Configuring explicitely useReleaseProfile parameter to true will force Maven Release Plugin 3 to work like version 2. It provides an easy but temporary solution, working only with Maven 3, when you can't yet write your own release profile.

          Mark Waite added a comment -

          Thanks very much for doing that investigation basil.

          olamy do you have a preference how we handle this? I think there are several options:

          Mark Waite added a comment - Thanks very much for doing that investigation basil . olamy do you have a preference how we handle this? I think there are several options: Revert https://github.com/jenkinsci/plugin-pom/pull/558 and https://github.com/jenkinsci/pom/pull/281 and wait until later to use maven release plugin 3.0.0 Retain https://github.com/jenkinsci/plugin-pom/pull/558 and https://github.com/jenkinsci/pom/pull/281 and add useReleaseProfile=true until later when a release profile can be defined Retain https://github.com/jenkinsci/plugin-pom/pull/558 and https://github.com/jenkinsci/pom/pull/281 and define a release profile that builds and attaches sources.jar and javadoc.jar

          Olivier Lamy added a comment -

          oops sorry for that. I have in mind we were using our own profile for releasing (my bad didn't check)

          my preference is definitely defining a release profile so we are totally independent from any changes in the maven plugin (note it's what Apache does for ages now see https://github.com/apache/maven-apache-parent/blob/fe33d11d29d217a1c7758163d8b4ca2d8093de70/pom.xml#L249 )

          I'm happy to provide a PR.

          Olivier Lamy added a comment - oops sorry for that. I have in mind we were using our own profile for releasing (my bad didn't check) my preference is definitely defining a release profile so we are totally independent from any changes in the maven plugin (note it's what Apache does for ages now see https://github.com/apache/maven-apache-parent/blob/fe33d11d29d217a1c7758163d8b4ca2d8093de70/pom.xml#L249 ) I'm happy to provide a PR.

          Basil Crow added a comment -

          Looks like the plugin parent POM already defines a jenkins-release profile and configures maven-release-plugin correctly, so the same logic just needs to be side-ported to the parent POM for Jenkins core and core components.

          Basil Crow added a comment - Looks like the plugin parent POM already defines a jenkins-release profile and configures maven-release-plugin correctly , so the same logic just needs to be side-ported to the parent POM for Jenkins core and core components.

          Olivier Lamy added a comment -

          PR https://github.com/jenkinsci/pom/pull/296

          I do not see any problem with plugin-pom as it already have a jenkins-release profile and use.

          Are you sure sources and javadoc are missing for plugins with this new parent?

          I made a release last of ldap plugin and I cannot see such problem (https://repo.jenkins-ci.org/artifactory/public/org/jenkins-ci/plugins/ldap/2.11/) 

          Olivier Lamy added a comment - PR  https://github.com/jenkinsci/pom/pull/296 I do not see any problem with plugin-pom as it already have a jenkins-release profile and use. Are you sure sources and javadoc are missing for plugins with this new parent? I made a release last of ldap plugin and I cannot see such problem ( https://repo.jenkins-ci.org/artifactory/public/org/jenkins-ci/plugins/ldap/2.11/)  

          Basil Crow added a comment -

          Basil Crow added a comment - Yeah, I realized that just a few minutes earlier: https://issues.jenkins.io/browse/JENKINS-69198?focusedCommentId=428739&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-428739

          Basil Crow added a comment -

          Basil Crow added a comment - https://github.com/jenkinsci/pom/pull/296 merged and released as https://github.com/jenkinsci/pom/releases/tag/jenkins-1.84 I plan to expedite https://github.com/jenkinsci/jenkins/pull/6954 in time for the 8/2 weekly release.

          Basil Crow added a comment -

          Merged toward the 2.362 weekly release

          Basil Crow added a comment - Merged toward the 2.362 weekly release

          Mark Waite added a comment -

          Fix confirmed in 2.362 release. Thanks very much basil and olamy!

          Retaining the lts-candidate label because we'll need this backported to Jenkins 2.361.1

          Mark Waite added a comment - Fix confirmed in 2.362 release. Thanks very much basil and olamy ! Retaining the lts-candidate label because we'll need this backported to Jenkins 2.361.1

            olamy Olivier Lamy
            markewaite Mark Waite
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: