I'd stick with map arguments for simple cases.  Even the example from the 
wiki is simpler if you use map.  

Move to the closure option once you have more experience or complex usage. 
 For example, the new (simplified) syntax for pipleline can be implemented 
as closure:

pipeline {
  stages {
    ...
  }

  postBuild {
  }
}

On Monday, September 19, 2016 at 5:30:46 AM UTC-7, Kenneth Baltrinic wrote:
>
> Trying to get my head around what is the best way to implement some custom 
> pipeline DLS commands using global functions 
> <https://github.com/jenkinsci/workflow-cps-global-lib-plugin#defining-global-functions>.
>  
> I am looking at the examples given under Defining a more structured DSL 
> <https://github.com/jenkinsci/workflow-cps-global-lib-plugin#define-more-structured-dsl>,
>  
> which shows an example of accepting arguments via variable assignments 
> inside of a closure.  Is this the preferred method?  It seems most build in 
> commands (git, sh, etc) accept a Map of arguments.  I am not a groovy 
> expert but am trying to understand why/when one approach is better than the 
> other?  Any thoughts or illumination on this would be appreciated.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ec7e04ba-f8c0-460b-9419-d1b0adc2390c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to