Re: Groovy Plugin VS Build Flow Plugin
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 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 jenkinsci-users+unsubscr...@googlegroups.com. 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Groovy Plugin VS Build Flow Plugin
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 UTC+1, Nicolas De loof wrote: 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 delb...@gmail.com javascript: 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 jenkinsci-use...@googlegroups.com javascript:. 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Groovy Plugin VS Build Flow Plugin
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 possible which I need)? I agree with the sentiment that either approach is somewhat confusing and harder than it would have to be. That is, build flow provides convenient high-level methods with a lot coding to handle error detection and reporting that you would have to duplicate in your own groovy code - in addition to understanding the full jenkins API in order to know what to do in raw groovy in the first place. But, using build flow means that you can't do anything else in that job and you need to run an assortment of other jobs and coordinate them by passing parameters around which also seems cumbersome.I think it would be nice to have the high-level methods for common operations - at least the things build flow would do - in a groovy library that would be usable directly without having to know all the details and that would work as an ordinary build step inside a job. -- Les Mikesell lesmikes...@gmail.com -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Groovy Plugin VS Build Flow Plugin
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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
