build flow is an orchestration plugin, not a scripting one. The DSL is
actually groovy based, but should be used only to trigger jobs.
2014/1/8 dev123 delber...@gmail.com
I have installed the Build Flow Plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
making the Build
Yes that make sense but it seems to me that the same functionality can be
achieved with the Groovy Plugin not as pretty though.
And why is the Build Environment removed from the Build Flow job type (e.g
Set Build Name is not possible which I need)?
On Thursday, January 9, 2014 9:37:34 AM
On Thu, Jan 9, 2014 at 4:17 AM, dev123 delber...@gmail.com wrote:
Yes that make sense but it seems to me that the same functionality can be
achieved with the Groovy Plugin not as pretty though.
And why is the Build Environment removed from the Build Flow job type (e.g
Set Build Name is not
I have installed the Build Flow Plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
making the Build Flow Job Type available. But this jobtype does not have
the *Build Environment *configuration like the other jobtypes (freestyle,
maven, etc.) which I need.
I have also
