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.
