[JIRA] Work started: (JENKINS-7900) Promoting a job should also promote all of it modules

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[JIRA] Work started: (JENKINS-7900) Promoting a job should also promote all of it modules

JIRA noreply@jenkins-ci.org

     [ http://issues.jenkins-ci.org/browse/JENKINS-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JENKINS-7900 started by Alan Harder.

> Promoting a job should also promote all of it modules
> -----------------------------------------------------
>                 Key: JENKINS-7900
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-7900
>             Project: Jenkins
>          Issue Type: New Feature
>          Components: promoted-builds-simple
>         Environment: Maven software project on Linux
>            Reporter: bkuder
>            Assignee: Alan Harder
> I have a hudson job that is based on a Maven software project. The hudson job builds a Maven parent POM file, that in turn builds several child modules. One of the child modules is "dist", which produces a zip file of the software distribution. My parent has no artifacts. The artifacts I am interested in are owned by the dist module.
> For example:
>   my-project
>   +-moduleA
>   +-moduleB
>   +-dist
> I use the promoted-simple-builds plugin in conjunction with the copy artifact plugin. When my-project is released, I use the promoted-simple-builds plugin to promote the build to "GA Release".
> Then, (in a separate Hudson job), I use the Copy artifacts plugin to copy the dist module's artifacts to a known directory.
> Unfortunately, it looks like only the parent job (my-project) is tagged as a "GA Release". The child modules do not appear to get tagged - and as a result, I can't use the Copy Artifact plugin to say "copy the artifacts from the last GA Release build of the dist module to directory X", as I get the following error:
> Building on master
> Unable to find a build for artifact copy from: my-project/my-project$dist
> Finished: FAILURE
> The Promotion drop down is not available from the module's build page by default. But, interestingly if I use this URL:
> http://my-hudson/job/my-project/706/my-project$dist/parent/parent/parent/plugin/promoted-builds-simple/makePromotable 
> Then, I can navigate to the module's build page and flag the individual module as "GA Release" - then the Copy Artifacts configuration works (which implies when dist is flagged as a "GA Release", then I can select it from Copy Artifact).
> However, this is a very manual process. And it seems that if a parent has been tagged as "Promoted", then it should be implied that all of the children have been "Promoted" as well.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira