Export to GitHub

build-pipeline-plugin - issue #80

Support the promote plugin


Posted on Jan 17, 2012 by Happy Elephant

When building a pipeline I miss some steps that is triggered by the Promote plugin.

The Promote plugin has the ability to trigger other builds when a build is promoted.

I our set-up we have jobs that trigger test jobs. The test jobs trigger a promote job after a successful test result. Then when a promote is done, the promote job might trigger others jobs that depend on promoted builds.

I would like that to be visible in the pipeline somehow.

Comment #1

Posted on Jun 18, 2012 by Swift Camel

(No comment was entered for this change.)

Comment #2

Posted on Dec 28, 2012 by Grumpy Wombat

I added bug 148 before I saw this. I have the same need for a similar situation.

If any post-promotion actions are defined that run downstream jobs, they are ignored by the build-pipeline plugin. If the same actions are defined as a post-build action they work. The promotion configs should be checked for pipelined actions in addition to the main config.xml for a job.

Comment #3

Posted on May 21, 2013 by Grumpy Dog

I took a look at this is and the reason it's not showing up is because the Build Pipeline plugin assumes all actions to be an exact instance of (not a subclass):

(action.getClass().equals(hudson.plugins.parameterizedtrigger.SubProjectsAction.class))

Anything else is ignored, and the Promoted Builds plugin (I think) adds PromotedProjectAction on which one could do getProcesses() and then look for getBuildSteps() and those may include a project. Didn't even get the source to properly get imported into IntelliJ, nor into Eclipse.

Comment #4

Posted on Jun 22, 2013 by Grumpy Hippo

Hi Fredrik, I don't seem to have a problem with intellij.

What are you seeing?

Comment #5

Posted on Jul 1, 2013 by Swift Panda

Hi everyone!

I was wondering if fredrik proposed solution fixes the issue... Have anyone tested it?

I really +1 this issue! :)

Thanks!

Comment #6

Posted on May 1, 2014 by Swift Bear

Hi

Is there a solution for this problem?

Thanks

Comment #7

Posted on May 1, 2014 by Massive Rhino

Hi Michael,

As Bruce alluded to above, you can workaround the issue by adding any builds that are started via a promotion action to your job's post-build actions as a "Build other project (Manual step)" action. This post-build action won't trigger the jobs, but it will allow the Build Pipeline to see the downstream jobs.

In my configuration I am fingerprinting artifacts. I'm not sure if that is required to employ this workaround.

Comment #8

Posted on Jul 22, 2014 by Quick Ox

It appears that I can only add a single Manual post-build action. Is that typical? If so, how can I display multiple promotion steps in my pipeline?

Additionally, in my promotions I call the same job multiple times with different parameters. However, with the work-around, the manual job only shows once, which is misleading. Any suggestions for that?

Ultimately, it would be ideal to have each individual promotion display in the Pipeline without having to have a bogus manual post-build action, so I'd love to see a fix for this.

Comment #9

Posted on Aug 26, 2014 by Grumpy Horse

To start multiple Manual post-build actions... Make it a comma delimited list of jobs you want to start ;-)

Comment #10

Posted on Aug 28, 2014 by Quick Ox

Guess that shoulda been obvious :-P Thanks.

Comment #11

Posted on Feb 26, 2015 by Quick Bird

This work around will show the downstream jobs trigger by promotion, but it doesn't really capture the flow logic where promotion happens only if a downstream job passes. It looks like the downstream jobs and the promotion triggered downstream jobs happened in parallel.

Status: New

Labels:
Type-Enhancement Priority-Medium