Jenkins › Jenkins issues

[JIRA] (JENKINS-14590) Redeploy Artifacts needs to executed for each module when it used redeploy all modules

Classic

List

Threaded

5 messages Options

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-14590) Redeploy Artifacts needs to executed for each module when it used redeploy all modules

Issue Type:	Bug
Assignee:	Unassigned
Components:	maven
Created:	26/Jul/12 7:44 PM
Description:	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.
Environment:	1.472
Project:	Jenkins
Priority:	Blocker
Reporter:	Jeff Maxwell

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-14590) Redeploy Artifacts needs to executed for each module when it used redeploy all modules

Change By:	Jeff Maxwell (24/Sep/12 6:01 PM)
Environment:	1. 472 461 and Above
Description:	Formerly you In versions prior to 1.461 one could redeploy all artifacts of a build with one click, now you need to redeploy each module separately 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 this is impossible. problematic, complicating promotion of a build from a staging to a release repository

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-14590) Redeploy Artifacts needs to executed for each module when it used redeploy all modules

In reply to this post by JIRA noreply@jenkins-ci.org

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

JIRA noreply@jenkins-ci.org

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

In reply to this post by JIRA noreply@jenkins-ci.org

Change By:	Jeff Maxwell (28/Sep/12 1:21 PM)
Summary:	Redeploy Artifacts needs to executed for each button no longer appears on main build page of multi- module when it used redeploy all builds, requiring individual reployment of modules

JIRA noreply@jenkins-ci.org

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

In reply to this post by JIRA noreply@jenkins-ci.org

Change By:

Jeff Maxwell (03/Jan/13 2:52 PM)

Description:

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}