Gift Guide
Customer Reviews for

Jenkins Continuous Integration Cookbook

Average Rating 4
( 1 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
Page 1 of 1
  • Posted July 21, 2012

    more from this reviewer

    compatible with ant, maven and groovy

    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.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews
Page 1 of 1