• Type: Bug
• Resolution: Unresolved
• Priority: Blocker
• Component/s: maven-plugin
• Labels:

  None
• Environment:

  1.461 and Above

[JENKINS-14590] Redeploy Artifacts button no longer appears on main build page of multi-module builds, requiring individual reployment of modules

Jeff Maxwell created issue - 2012-07-26 19:44

Jeff Maxwell made changes - 2012-09-24 18:01

Description	Original: Formerly you could redeploy all artifacts of a build with one click, now you need to redeploy each module separately. In multi-module projects this is impossible.	New: In versions prior to 1.461 one could redeploy all artifacts of a build from the build page from the "Redeploy Artifacts" button. In 1.461 and above the "Redeploy Artifacts" button no longer appears on the root build page and only appears on each component page. This appears to be caused this section: {code} <hudson.maven.reporters.MavenAggregatedArtifactRecord>   <records/>   <parent reference="../../.."/ </hudson.maven.reporters.MavenAggregatedArtifactRecord> {code} no longer appearing in the build.xml. This bug makes redeploying large multi-module projects problematic, complicating promotion of a build from a staging to a release repository
Environment	Original: 1.472	New: 1.461 and Above

Collapse comment: Jeff Maxwell added a comment - 2012-09-24 18:02

Jeff Maxwell added a comment - 2012-09-24 18:02

This is blocking us from migrating to newer versions of Jenkins.

Expand comment: Jeff Maxwell added a comment - 2012-09-24 18:02

Jeff Maxwell added a comment - 2012-09-24 18:02 This is blocking us from migrating to newer versions of Jenkins.

Jeff Maxwell made changes - 2012-09-28 13:21

Summary

Original: Redeploy Artifacts needs to executed for each module when it used redeploy all modules

New: Redeploy Artifacts button no longer appears on main build page of multi-module builds, requiring individual reployment of modules

Jeff Maxwell made changes - 2013-01-03 14:52

Description

Original: In versions prior to 1.461 one could redeploy all artifacts of a build from the build page from the "Redeploy Artifacts" button. In 1.461 and above the "Redeploy Artifacts" button no longer appears on the root build page and only appears on each component page. This appears to be caused this section: {code} <hudson.maven.reporters.MavenAggregatedArtifactRecord>   <records/>   <parent reference="../../.."/ </hudson.maven.reporters.MavenAggregatedArtifactRecord> {code} no longer appearing in the build.xml. This bug makes redeploying large multi-module projects problematic, complicating promotion of a build from a staging to a release repository

New: In versions prior to 1.461 one could redeploy all artifacts of a build from the build page from the "Redeploy Artifacts" button. In 1.461 and above the "Redeploy Artifacts" button no longer appears on the root build page and only appears on each component page. This appears to be caused this section: {code} <hudson.maven.reporters.MavenAggregatedArtifactRecord>   <records/>   <parent reference="../../.."/ </hudson.maven.reporters.MavenAggregatedArtifactRecord> {code} no longer appearing in the build.xml. This bug makes redeploying large multi-module projects problematic, complicating promotion of a build from a staging to a release repository h4. Workaround Using a post build groovy step similar to the code below: {code} def mavenModuleSetBuild = Thread.currentThread().executor.executable; mavenModuleSetBuild.addAction(new MavenAggregatedArtifactRecord(mavenModuleSetBuild)); {code}

R. Tyler Croy made changes - 2016-07-25 23:50

Workflow

Original: JNJira [ 145275 ]

New: JNJira + In-Review [ 176303 ]