Pipeline Best Practices

Issue

  • Any best practices are welcome for pipeline implementation

Environment

  • Jenkins
  • CloudBees Jenkins Enterprise - Managed Master (CJEMM)
  • CloudBees Jenkins Team (CJT)
  • CloudBees Jenkins Platform - Client Master (CJPCM)
  • Pipeline plugin

Resolution

BEST PRACTICES is the entry point which contains a collection of tips, advice, gotchas and other best practices for using the Jenkins Pipeline plugin.

The following points aim to extend BEST PRACTICES with additional info related to CloudsBees Features and Support.

  • The most up-to-date documentation is under <JENKINS_URL>/pipeline-syntax.

a. Step Reference: <JENKINS_URL>/pipeline-syntax/html

b. Global Variables Reference: <JENKINS_URL>/pipeline-syntax/globals

  • Be sure to frequently check for Pipeline Plugin updates and keep current on updating your environment(s) with recent bug fixes and feature improvements.

  • Place a Checkpoint before a high risk operation. If the build fails, Checkpoint allows the build to be resumed from the checkpoint just before the failure.

Articles and Presentations

Find below list of references which contains a compilation of best practices. Some of them has already mentioned above.

Jenkins World presentations:

Goodies:

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.