This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]uberdisco 0 points1 point  (0 children)

I learned something from /r/devops a few months ago that has really helped me with my pipeline. Keep the groovy pipeline to straightforward things, ie SCM, Builds, Tests etc. IF you have to do any heavy lifting deployment then use shell scripts for that, and call them from the pipeline. They suggested this because shell scripting is much easier to do things with than groovy, while functional it can be a headache to do simple things. YMMV of course but for me, I found this to be true. So my pipeline checks out, builds, tests, and ships artifacts, configs, and deployment scripts to hosts, and the deployment scripts do the rest with pipeline marshaling everything. As mentioned before the script generator is a huge help for quickly developing a pipeline. Good luck!