search

ganesansays / build-pipeline-plugin

Automatically exported from code.google.com/p/build-pipeline-plugin
0 stars 0 forks source link

Support the promote plugin #80

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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.

Original issue reported on code.google.com by pablaa...@gmail.com on 17 Jan 2012 at 9:40

GoogleCodeExporter commented 9 years ago

Original comment by marc...@centrumsystems.com.au on 18 Jun 2012 at 5:47

GoogleCodeExporter commented 9 years ago 
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.

Original comment by bruce.e...@gmail.com on 28 Dec 2012 at 12:29

GoogleCodeExporter commented 9 years ago 
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.

Original comment by fredrik....@squeed.com on 21 May 2013 at 12:28

GoogleCodeExporter commented 9 years ago 
Hi Fredrik,  I don't seem to have a problem with intellij.

What are you seeing?

Original comment by geo...@centrumsystems.com.au on 22 Jun 2013 at 3:36

GoogleCodeExporter commented 9 years ago 
Hi everyone! 

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

I really +1 this issue! :)

Thanks!

Original comment by gerar...@gmail.com on 1 Jul 2013 at 3:59

GoogleCodeExporter commented 9 years ago 
Hi

Is there a solution for this problem?

Thanks

Original comment by michael....@gmail.com on 1 May 2014 at 11:08

GoogleCodeExporter commented 9 years ago 
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.

Original comment by sieverssj@gmail.com on 1 May 2014 at 11:51

GoogleCodeExporter commented 9 years ago 
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.

Original comment by caoimhi...@gmail.com on 22 Jul 2014 at 3:56

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

Original comment by peter.pa...@randstadgroep.nl on 26 Aug 2014 at 9:02

GoogleCodeExporter commented 9 years ago 
Guess that shoulda been obvious :-P Thanks.

Original comment by caoimhi...@gmail.com on 28 Aug 2014 at 2:19

GoogleCodeExporter commented 9 years ago 
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.

Original comment by jch...@netflix.com on 26 Feb 2015 at 7:20