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 <[email protected]> > 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 installed the Groovy plugin: > https://wiki.jenkins-ci.org/display/JENKINS/Groovy+plugin > > which I can enable in e.g a freestyle project as a build step. It seems > that you can more or less do the same with the Groovy Plugin (in e.g a > freestyle project) as with the Build Flow plugin + you have access to the > Build Environment configuration. > > Is there anything that the build flow plugin gives besides some wrapped > groovy methods like : parallel, ignore etc. that I cannot do with the > Groovy Plugin? > > In short what are the most significant differences between the Groovy > plugin and the Build Flow plugin when it comes to functionality? > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
