On Wednesday, February 25, 2015 at 6:22:57 PM UTC-5, Jesse Glick wrote: > > On Thursday, February 5, 2015 at 4:30:11 AM UTC-5, Christoph VogtlÃĪnder > wrote: >> >> I want to use the workflow plugin and together with the "Prepare an >> environment for the run" feature provided by the EnvInject plug in. >> > > EnvInject is probably useless for Workflow. > > I find envinject useful. I use it to inject the cause of the build into the build phase, so I can set the build description to something meaningful to my users. My users like to know who triggered a build by looking at the build history. When I tried that with Workflow, it did not work. Is there a way to access the build cause(s) in a workflow?
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6c986d7a-75e1-469f-b348-97e8d4dd1b93%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
