The Jenkins specific tasks should be mostly single purpose and logicless in my view.
The complex logic should be testable outside of Jenkins. But building complex logic in groovy "just because it is there" and not "because we cannot do it elsewhere" is the problem my rant is directed at On Friday 27 May 2016, Maciej Jaros <mac...@mol.com.pl> wrote: > Stephen Connolly (2016-05-27 12:12): > > > > On 27 May 2016 at 07:59, Craig Rodrigues <rodr...@freebsd.org > <javascript:_e(%7B%7D,'cvml','rodr...@freebsd.org');>> wrote: > >> Hi, >> >> The new Jenkins UI looks nice, and will be a big improvement over the >> existing UI. >> >> The original selling point of Jenkins was that even with the simplistic >> forms-based UI, >> someone could fill out a relatively simple form, and have a continuous >> integration pipeline. >> I have met people who were general devops and scripting people, and could >> use Jenkins quite nicely. >> >> While I understand the motivation for Pipeline (previously known as >> Workflow), I can't say I'm very happy with the results. >> >> Here are some of the pain points I've encountered with Pipeline scripts: >> >> - Other than the most trivial of scripts, you need to be a >> knowledgable Groovy programmer. For example, to make a global variable, >> you need to use a @Field. (What?!) Most scripting and devops people that >> I know don't really know Groovy. >> >> So in my personal opinion, this is a sign of People Doing Things Wrong™ > > By this I mean that your Jenkinsfile should *not* be doing complex things. > You should have shell scripts or equivalent to do the complex > functionality. That lets you test each individual step in the phase on > local developer machines. Then your pipeline should end up mostly being > > > But you cannot test everything locally, because you e.g. don't have build > parameters, you might not have certain SSH credentials defined... That said > I do tend to move everything to scripts, but this really defeats the > purpose of almost all Jenkins plugins... And plugins gives you some > integrations (especially with credentials) you don't have in scripts. And > it's much easier to add build step for triggering e.g. call of another > project and passing all parameters to it from current build (which BTW is > overly hard with Groovy). > > Regards, > Nux. > > -- > 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 > <javascript:_e(%7B%7D,'cvml','jenkinsci-users%2bunsubscr...@googlegroups.com');> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/fac125e7-9e6c-46f1-bbe7-42067660d98c%40mol.com.pl > <https://groups.google.com/d/msgid/jenkinsci-users/fac125e7-9e6c-46f1-bbe7-42067660d98c%40mol.com.pl?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- 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/CA%2BnPnMxSo6%3D9WaaBUZYxdYfMsj%3DRgbcrQyO3F3J%3D2oUuXcuoFA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
