Jenkins Continuous Integration Cookbook

Being a cookbook, this is good for referencing. It doesn't neglect best practice which was a notable take-away. Had a few head-scratchers deciphering some recipe steps.

This book has some amazing examples of Groovy coding, plug-in integration, and recommendations on how to "glue" them together. Not for the newbie though. The depth of the recipe's is moderate to deep, and very useful once you have a grasp on all the principles involved.

The Jenkins package is a worthy attempt to streamline and as much as possible automate the bookkeeping steps in doing software development. The latter has many implementations, as you probably well know. Like agile, or some other rapid application development protocol. What Jenkins is especially geared towards is the cycle of bug fixing.Chapter 2 is about security in Jenkins. But I'm guessing that this is a secondary consideration. If your team is developing within a private network, firewalled from the Internet, then you should focus on the rest of the book, which is actually about using Jenkins per se.Other parts of the book show compatibility with Maven, Ant and Groovy. Packages that are already highly in use. Commendably, the book warns that if you use Jenkins with Maven, not to put too much of the configuration commands into Jenkins, in order to build, test and deploy outside Jenkins. Since Maven can be well suited for that. The text gives a lengthy discussion of how to make the Maven pom.xml file be readable by Jenkins, for compatibility.For more advanced developers who have chosen to use Groovy, there are also examples. These involve more powerful commands, all encoded as XML. Certain sections of the book are really more about the use of Groovy and Maven, instead of Jenkins, and can be read as such. You also get indirect advice about abandoning Ant, as being too low level for current code development.Interestingly, some effort has gone into having Jenkins be able to do customised look and feel and to make its reports as understandable as possible. Hard core developers probably don't need any of this. But it is useful to upper management to see a consistent corporate branding.

Vom cookbook erwartet man viel mehr als was da drin ist. Ich empfehle niemanden das Buch zu kaufen. Spart euch das Geld.