Jenkins Continuous Integration Cookbook

Preface 1
Chapter 1: Maintaining Jenkins 9
Introduction 10
Using a test Jenkins instance 11
Backing up and restoring 16
Modifying the Jenkins configuration from the command line 21
Installing Nginx 24
Configuring Nginx as a reverse proxy 28
Reporting overall storage use 33
Deliberately failing builds through log parsing 36
Adding a job to warn of storage use violations through log parsing 39
Keeping in contact with Jenkins through Firefox 42
Monitoring via JavaMelody 45
Keeping track of script glue 49
Scripting the Jenkins CLI 50
Global modifications of jobs with Groovy 53
Signaling the need to archive 55
Chapter 2: Enhancing Security 
Introduction 
Testing for OWASP\'s top 10 security issues 
Finding 500 errors and XSS attacks in Jenkins through fuzzing 
Improving security via small configuration changes 
Avoiding sign-up bots with JCaptcha 
Looking at the Jenkins user through Groovy 
Working with the Audit Trail plugin 
Installing OpenLDAP 
Using Script Realm authentication for provisioning 
Reviewing project-based matrix tactics via a custom group script 
Administering OpenLDAP 
Configuring the LDAP plugin 
Installing a CAS server 
Enabling SSO in Jenkins 
Exploring the OWASP Dependency-Check plugin 

Chapter 3: Building Software  111
Chapter 4: Communicating Through Jenkins  167
Chapter 5: Using Metrics to Improve Quality  209
Introduction 111
Plotting alternative code metrics in Jenkins 
115
Running Groovy scripts through Maven 
120
Manipulating environmental variables 
125
Running Ant through Groovy in Maven 
129
Failing Jenkins jobs based on JSP syntax errors 
134
Configuring Jetty for integration tests 
138
Looking at license violations with Rat 
142
Reviewing license violations from within Maven 
144
Exposing information through build descriptions 
149
Reacting to generated data with the groovy-postbuild plugin 
152
Remotely triggering jobs through the Jenkins API 
155
Adaptive site generation 
158
Introduction 
Skinning Jenkins with the simple themes plugin 
Skinning and provisioning Jenkins using a WAR overlay 
Generating a home page 
Creating HTML reports 
Efficient use of views 
Saving screen space with the Dashboard View plugin 
Making noise with HTML5 browsers 
An extreme view for reception areas 
Mobile presentation using Google Calendar 
Mobile apps for Android and iOS 
Knowing your audience with Google Analytics 
Simplifying powerful visualizations using the R plugin 
Introduction 
Estimating the value of your project through sloccount 
Looking for \"smelly\" code through code coverage 
Activating more PMD rulesets 
Creating custom PMD rules 
Finding bugs with FindBugs 
Enabling extra FindBug rules 
Finding security defects with FindBugs 
Verifying HTML validity 
Reporting with JavaNCSS 
Checking code style using an external pom.xml file 
Faking Checkstyle results 
Integrating Jenkins with SonarQube 
Analyzing project data with the R plugin 
Chapter 6: Testing Remotely  263
Chapter 7: Exploring Plugins  317
Introduction 
Deploying a WAR file from Jenkins to Tomcat 
Creating multiple Jenkins nodes 
Custom setup scripts for slave nodes 
Testing with FitNesse 
Activating FitNesse HtmlUnit fixtures 
Running Selenium IDE tests 
Triggering failsafe integration tests with Selenium WebDriver 
Creating JMeter test plans 
Reporting JMeter performance metrics 
Functional testing using JMeter assertions 
Enabling Sakai web services 
Writing test plans with SoapUI 
Reporting SoapUI test results 
Introduction 317
Personalizing Jenkins 
319
Testing and then promoting builds 
322
Fun with pinning JSGames 
327
Looking at the GUI samples plugin 
329
Changing the help of the FileSystem SCM plugin 
332
Adding a banner to job descriptions 
336
Creating a RootAction plugin 
341
Exporting data 
344
Triggering events on startup 
346
Groovy hook scripts and triggering events on startup 
348
Triggering events when web content changes 
353
Reviewing three ListView plugins 
355
Creating my first ListView plugin 
359
iii
www.it-ebooks.infoTable of Contents
Appendix: Processes that Improve Quality  367
Index  383
Fail early 
Data-driven testing 
Learning from history 
Considering test automation as a software project 
Visualize, visualize, visualize 
Conventions are good 
Test frameworks and commercial choices are increasing 
Offsetting work to Jenkins nodes 
Starving QA/integration servers 
Avoiding human bottlenecks 
Avoiding groupthink 
Training and community 
Visibly rewarding successful developers 
Stability and code maintenance 
Resources on quality assurance 
And there\'s always more 
Final comments