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

Make Jenkins aware of the release artifacts.

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • m2release-plugin
    • None

      Jenkins currently is unaware of the artifacts produced by the release build as manve forks.

      It would be usefull if jenkins somehow was made aware of these artifacts and recorded them along with the other artifacts.

          [JENKINS-7487] Make Jenkins aware of the release artifacts.

          James Nord created issue -

          aristedes added a comment -

          Is this really a bug? I seem to have no trouble seeing the right artifacts in Jenkins.

          aristedes added a comment - Is this really a bug? I seem to have no trouble seeing the right artifacts in Jenkins.
          James Nord made changes -
          Link New: This issue is blocking JENKINS-10104 [ JENKINS-10104 ]

          Justin Smith added a comment -

          We also do not see the usual build artifacts when running the release plugin, in fact, the only thing in the successful build directory is the archived pom for the top-level project.

          We have the disk usage reporting turned on, and Jenkins is reporting incorrect workspace size for the release executions (around 5 mb) whereas the normal build workspace is usually 512mb, this may be an entirely different issue though...

          Justin Smith added a comment - We also do not see the usual build artifacts when running the release plugin, in fact, the only thing in the successful build directory is the archived pom for the top-level project. We have the disk usage reporting turned on, and Jenkins is reporting incorrect workspace size for the release executions (around 5 mb) whereas the normal build workspace is usually 512mb, this may be an entirely different issue though...

          lesterp added a comment -

          We see similar behavior. To add to what Justin sees above, if we don't check "Disable automatic artifact archiving" under the Maven Build step, and let Jenkins grab the artifacts per module, what gets saved after running the release plugin is the initial SNAPSHOT artifact of the project (from release:prepare, I believe).

          If we check "Disable automatic artifact archiving" and add a post-build step to archive the artifacts we want, it saves the correct 'release' (non-SNAPSHOT) artifacts, but the Jenkins fingerprints for the artifacts are invalid: "The fingerprint xxxxxxx did not match any of the recorded data."

          lesterp added a comment - We see similar behavior. To add to what Justin sees above, if we don't check "Disable automatic artifact archiving" under the Maven Build step, and let Jenkins grab the artifacts per module, what gets saved after running the release plugin is the initial SNAPSHOT artifact of the project (from release:prepare, I believe). If we check "Disable automatic artifact archiving" and add a post-build step to archive the artifacts we want, it saves the correct 'release' (non-SNAPSHOT) artifacts, but the Jenkins fingerprints for the artifacts are invalid: "The fingerprint xxxxxxx did not match any of the recorded data."

          tuomas_kiviaho added a comment -

          Kohsuke gave a nice presentation over Jenkins Maven Repository Plugin at JFokus and I got anxious to give it another try. Too bad that the releases weren't visible.

          tuomas_kiviaho added a comment - Kohsuke gave a nice presentation over Jenkins Maven Repository Plugin at JFokus and I got anxious to give it another try. Too bad that the releases weren't visible.
          tuomas_kiviaho made changes -
          Link New: This issue is related to JENKINS-9034 [ JENKINS-9034 ]
          James Nord made changes -
          Description Original: Hudson currently is unaware of the artifacts produced by the release build as manve forks.

          It would be usefull if hudson somehow was made aware of these artifacts and recorded them along with the other artifacts.           		New: Jenkins currently is unaware of the artifacts produced by the release build as manve forks.

          It would be usefull if jenkins somehow was made aware of these artifacts and recorded them along with the other artifacts.
          Summary Original: Make hudson aware of the release artifacts. New: Make Jenkins aware of the release artifacts.

          Patrick Pfeifer added a comment -

          How can this be done technically? I really miss the feature and might start working on it if somebody could give me a few hints.

          Patrick Pfeifer added a comment - How can this be done technically? I really miss the feature and might start working on it if somebody could give me a few hints.

          James Nord added a comment -

          My thoughts for this involved adding a new mojo to the maven release plugin. (release:checkout). The second part wood be to do the release:prepare RELEASE:checkout in a pre build then changing the pom to use to target/checkout/name_of_pom.xml

          James Nord added a comment - My thoughts for this involved adding a new mojo to the maven release plugin. (release:checkout). The second part wood be to do the release:prepare RELEASE:checkout in a pre build then changing the pom to use to target/checkout/name_of_pom.xml

            Unassigned Unassigned
            teilo James Nord
            Votes:
            7 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: