4 ms·
As the website got HN'd, a question: does Jenkins support now pass-through of parameters in pre/post build actions to other jobs? Background: I have "deploy fr
by mschuster91 11y ago
As the website got HN'd, a question: does Jenkins support now pass-through of parameters in pre/post build actions to other jobs?
Background: I have "deploy frontend" and "deploy backend" job, both of which need to invalidate some layers of caching, and a job parameter that specifies the environment (it's the docroot).
For now I have a metric shitload of shared code between the jobs as there is no way to move the cache clearing code to its own job and pass the environment parameter through in pre/post build actions.
- zzzeek 11y agoI can't imagine what you couldn't accomplish using the Parameterized Trigger Plugin https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Tr...
- mschuster91 11y agoCool, thanks for that. I'll mail this one to our infrastructure team, but it's sad to see that this isn't installed by default.
- zzzeek 11y agohow does it being an optional plugin change anything vs. Jenkins having every possible useful thing pre-installed resulting in a much more complicated setup screen? Plugin architecture is total win IMHO.
- mschuster91 11y agoParameters without the ability to pass them on is kind of pointless, imho the right solution is to provide a single "parametrization" plugin.