Report
![Cloudbees The Top 10 Best Practices for Jenkins Pipeline Plugin]()
The Top 10 Best Practices for Jenkins Pipeline Plugin
Follow this guidance to use it more efficiently and effectivelyThere are tricks and techniques to every form of technology and Jenkins Pipeline is no different. Many of the issues someone may come accross using Jenkins may be traced back to misuse or poor Syntax scripting. This helpful Infographic explains where you may be going wrong and what basic changes can be made to avoid common pitfalls.
Report Snap Shot
- Store Pipeline definitions in a SCM
- Don’t use shared libraries (the wrong way)
- Wrap your input in a timeout
- Avoid Script Security exceptions
