Extending the BuildResultTrigger plugin to filter on upstream parameters

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

Extending the BuildResultTrigger plugin to filter on upstream parameters

Jacqueline Roberti
Hello,

I would like the BuildResultTrigger plugin (https://github.com/jenkinsci/buildresult-trigger-plugin) to be extended to have an option to trigger on the success of another build PROVIDED that build has certain parameters.  

I work on a product that is composed of many microservices that all deploy in the same way.  Thus, it is beneficial to have a single, generic deploy job that relies on certain parameters.  However, some downstream jobs should only be triggered for certain services.  Rather than bloat the deploy job with lots of conditionals for specific downstream jobs, I would like to have a trigger in the downstream job.  The BuildResultTrigger plugin was the closest I could find, but it does not have the capacity to look at an upstream job’s parameters and filter on them.

I am happy to work on the development of this myself, or work with one of your developers.  

Thank you,
--
Jacqueline Roberti
Associate DevOps Engineer



--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B9A434F5-7317-472C-B116-576CA7C188EF%40broadinstitute.org.
For more options, visit https://groups.google.com/d/optout.

signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Extending the BuildResultTrigger plugin to filter on upstream parameters

Baptiste MATHUS
Hello Jacqueline,

Well, if you need to make some plugin extensible, what you propose seems the way to go.

Then propose a code modification to the plugin using a PR. I would strongly recommend you use that modified plugin internally and develop the custom extension and make it run in your production for some time before proposing the PR. That would avoid to think about making the plugin extensible just on a design doc, then realize when things go real that you missed something.

And/or ideally, you would show the implementation of that extension point in your product somewhere, but I seem to understand this is a proprietary one.

My 2 cents

2017-03-20 16:33 GMT+01:00 Jacqueline Roberti <[hidden email]>:
Hello,

I would like the BuildResultTrigger plugin (https://github.com/jenkinsci/buildresult-trigger-plugin) to be extended to have an option to trigger on the success of another build PROVIDED that build has certain parameters.  

I work on a product that is composed of many microservices that all deploy in the same way.  Thus, it is beneficial to have a single, generic deploy job that relies on certain parameters.  However, some downstream jobs should only be triggered for certain services.  Rather than bloat the deploy job with lots of conditionals for specific downstream jobs, I would like to have a trigger in the downstream job.  The BuildResultTrigger plugin was the closest I could find, but it does not have the capacity to look at an upstream job’s parameters and filter on them.

I am happy to work on the development of this myself, or work with one of your developers.  

Thank you,
--
Jacqueline Roberti
Associate DevOps Engineer



--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B9A434F5-7317-472C-B116-576CA7C188EF%40broadinstitute.org.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5d%3DWWQLhVf8_N%3DpFk3YZLmcDjNZDv3aJyvN-RDqbi-Aw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.