It's not so hard, it's just some behavior/limitations that are a bit hard to grasp (groovy loop anyone). I think they went on a road to provide some features at high trade back cost.
If you want some examples more like real life usage: https://github.com/jenkinsci/pipeline-examples I would love to have better or complex examples, that would save a lots of questions on this lists and people wouldn't get so frustrated trying to achieve simple stuff. Some people must have made a few .groovy that could be used by many, that would be great if that could be shared between user, like plugins one day. I made a few python scripts to help me back into the Jenkins non pipeline era, I still use them, but passing them to Groovy would be a pain, since even if I made a normal groovy script, I would still have to validate the Jenkins 'groovy' alike language can output the same thing and probably have to allow a few dozen of functions into scripts approval. So far, I use simple Jenkins file that launch a lot of console cmd (Python code, msbuild command, batch/bash script, custom C# program) that I can test into console. Work fine, except the Windows slave hang and the new email-ext that doesn't resolve the absolute path on node. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/de3f954b-71d6-43d0-8c25-adc475557136%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
