Re: Build Flow Plugin (pre-release 0.11): Change in SCM behavior?
On Wed, Oct 30, 2013 at 7:48 AM, nicolas de loof wrote: > scriptler is for groovy scripts > build flow is (supposed to) offer a DSL to orchestrate job execution > > both make sense. Maybe you're looking for something "in the middle" I'd like to create a more versatile 'matrix build' where the top-level job can be triggered by an scm change and can collect the results from child jobs into its own workspace.I think that could be done by build-flow with separate helper jobs to start the run and collect the results, but that seems messy and wrong. And it could be done in pure groovy, but no one here knows the language well enough to do a good job of dealing with all the possible error conditions, etc. I think it would be great if the operations that build[-flow provides were packaged as library routines you could use in a groovy build step. I haven't looked at scriptler yet - if it has a simple way to run other jobs in parallel and access their results that may be what I need. -- 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.
Re: Build Flow Plugin (pre-release 0.11): Change in SCM behavior?
scriptler is for groovy scripts build flow is (supposed to) offer a DSL to orchestrate job execution both make sense. Maybe you're looking for something "in the middle" 2013/10/30 Les Mikesell > On Wed, Oct 30, 2013 at 2:35 AM, nicolas de loof > wrote: > > Workspace support has indeed been removed > > Too many user use build-flow DSL as a groovy script console, that is > another > > topic (-> scriptler plugin) > > I'm still missing what would be wrong with having the build-flow > syntax available in a normal jenkins job that could poll an scm and > collect final results. Haven't looked at scripler, though. Does it > provide all the same operations and compact notation? > > -- >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. > -- 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: Build Flow Plugin (pre-release 0.11): Change in SCM behavior?
On Wed, Oct 30, 2013 at 2:35 AM, nicolas de loof wrote: > Workspace support has indeed been removed > Too many user use build-flow DSL as a groovy script console, that is another > topic (-> scriptler plugin) I'm still missing what would be wrong with having the build-flow syntax available in a normal jenkins job that could poll an scm and collect final results. Haven't looked at scripler, though. Does it provide all the same operations and compact notation? -- 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.
Re: Build Flow Plugin (pre-release 0.11): Change in SCM behavior?
Workspace support has indeed been removed Too many user use build-flow DSL as a groovy script console, that is another topic (-> scriptler plugin) For your use case, if you need to poll SCM with a workspace, use another upstream job 2013/10/30 Mike Dougherty > I'm using a custom built version of the plugin (using the code from this > PR: https://github.com/jenkinsci/build-flow-plugin/pull/40). As you can > see from the commit history, this is based on the unreleased 0.11 version. > > In my further exploration of this plugin (and the new version I had built) > I realized the build flow job no longer performs SCM operations, which I > was previously depending on for providing information (primarily git hash) > to the triggered builds. You can see my script here: > https://gist.github.com/mikedougherty/7227911 > > After some investigation I found this commit: > https://github.com/jenkinsci/build-flow-plugin/commit/444097d > which clearly shows that the plugin was intentionally changed to remove > SCM operation. However, now I'm unable to provide the required information > to the triggered builds. > > I'm not 100% clear on why this behavior was changed. Aside from my > particular issue it seems to specialize the plugin even further away from > what I know as 'standard' jenkins build capabilities. I must admit I > struggled at first with the inability to add a pre-step before performing > the flow script. At a higher level, I don't understand why this is a > separate job type instead of a possible build step to be added to (e.g.) a > free-form project. > > I'd appreciate any insight into the purpose of this change. Any info about > the design of the plugin would be helpful aid my understanding as well. > > For now I'm afraid I'll have to use 0.10 with the customized retry() > function. > > thanks! > > -- > 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.
Build Flow Plugin (pre-release 0.11): Change in SCM behavior?
I'm using a custom built version of the plugin (using the code from this PR: https://github.com/jenkinsci/build-flow-plugin/pull/40). As you can see from the commit history, this is based on the unreleased 0.11 version. In my further exploration of this plugin (and the new version I had built) I realized the build flow job no longer performs SCM operations, which I was previously depending on for providing information (primarily git hash) to the triggered builds. You can see my script here: https://gist.github.com/mikedougherty/7227911 After some investigation I found this commit: https://github.com/jenkinsci/build-flow-plugin/commit/444097d which clearly shows that the plugin was intentionally changed to remove SCM operation. However, now I'm unable to provide the required information to the triggered builds. I'm not 100% clear on why this behavior was changed. Aside from my particular issue it seems to specialize the plugin even further away from what I know as 'standard' jenkins build capabilities. I must admit I struggled at first with the inability to add a pre-step before performing the flow script. At a higher level, I don't understand why this is a separate job type instead of a possible build step to be added to (e.g.) a free-form project. I'd appreciate any insight into the purpose of this change. Any info about the design of the plugin would be helpful aid my understanding as well. For now I'm afraid I'll have to use 0.10 with the customized retry() function. thanks! -- 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.
