Skip to content

Jenkins World 2017 - The Game of DevOps: Applying Jenkins Best Practices in a Dynamic Industry http://sched.co/ALOY

License

Notifications You must be signed in to change notification settings

v1v/JenkinsWorld2017

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Jenkins World 2017

This talk was presented during Jenkins World 2017 in San Francisco, CA on August 29th-31st.

Presentation

2017_Jenkins_World_VictorMartinez.pdf contains the slides of the presentation.

NOTE: The presentation was recorded although the video URL hasn't been released yet.

Best Practices

You can find some example groovy scripts to analyse what Jenkins projects don't follow those practices.

It does use the internal Jenkins API and therefore you need to be cautious to avoid doing evil things:

Bear in mind, some of those scripts are just read only but others are also adding some details in the project description and also disabling those jobs.

This groovy implementation is just a basic/simple implementation, it might not cover all the use cases. The final solution was implemented as a Jenkins Plugin called Jenkins Lint plugin.

  • Example 1 - shows list of projects without any description
  • Example 2 - shows list of projects with whitespaces in their name
  • Example 3 - shows list of projects without any label restriction
  • Example 4 - shows list of projects without any workspace cleanup policy
  • Example 5 - shows list of projects without any log rotator policy or empty values
  • Example 6 - shows list of projects using polling
  • Example 7 - shows list of projects which use git but no shallow cloning
  • Example 8 - shows list of projects which use git but no git reference repos
  • Example 9 - shows list of Projects which some system exit when using groovy post build actions
  • Example 10 - shows list of pipelines without the groovy sandbox option
  • Example 11 - shows list of Maven job types
  • Example 12 - shows list of projects which don't use the Build Timeout plugin
  • Example 13 - shows list of projects which don't use the Build Failure plugin

How to run them

  • Open the script console page: This feature can be accessed from the "manage Jenkins" link, typically at your http://server/jenkins/script. ScriptConsole Wiki
  • Copy one of those groovy Script and paste in the script console text area.
  • Run and look at the output.

Further details

For more information on JenkinsLint, please visit JenkinsLint.

There are even further examples of using the internal Jenkins API in the below links:

About

Jenkins World 2017 - The Game of DevOps: Applying Jenkins Best Practices in a Dynamic Industry http://sched.co/ALOY

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages