OK, so I'm starting to get the hint that this isn't interesting to people. :)
Other than modifying
"hudson.plugins.parameterizedtrigger.BuildInfoExporterAction", is
there some other way to force the plugin to export details about the
builds it triggered for later build steps? I'm hoping that I don't
have to maintain a fork of the ParameterizedTriggerPlugin.
Thanks!
Brian
On Tue, Feb 14, 2012 at 4:59 PM, Brian Parker <
[hidden email]> wrote:
> Can one someone please give me some feedback on if they think having
> the ParameterizedTriggerPlugin add the triggered builds to the
> environment for later build steps is a good idea? I've created
>
https://issues.jenkins-ci.org/browse/JENKINS-12488 .
>
> I've created a pull request for that issue and also a new
> ParameterFactory -
>
https://github.com/jenkinsci/parameterized-trigger-plugin/pull/16>
> If you don't want the LinesFromFileParameterFactory, I think I can
> always package that as a separate plugin that depends on the
> ParameterizedTriggerPlugin. However, I don't know how else we'll
> accomplish our goals without something similar to JENKINS-12488. For
> that reason, I'm kind of eager for some feedback. Please let me know
> what you think.
>
> Thank you!
>
> Brian
Locked
