Jenkins Continuous Integration Cookbook

( 1 )

Overview

If you are a Java developer, software architect, technical project manager, build manager, or development or QA engineer, this Cookbook is for you.

You should have a basic understanding of the Software Development Life Cycle and Java development, as well as a rudimentary understanding of Jenkins.

This ...

See more details below
Paperback
$43.29
BN.com price
(Save 3%)$44.99 List Price
Other sellers (Paperback)
  • All (5) from $47.22   
  • New (4) from $47.22   
  • Used (1) from $48.68   
Jenkins Continuous Integration Cookbook

Available on NOOK devices and apps  
  • NOOK Devices
  • Samsung Galaxy Tab 4 NOOK
  • NOOK HD/HD+ Tablet
  • NOOK
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac

Want a NOOK? Explore Now

NOOK Book (eBook)
$26.99
BN.com price

Overview

If you are a Java developer, software architect, technical project manager, build manager, or development or QA engineer, this Cookbook is for you.

You should have a basic understanding of the Software Development Life Cycle and Java development, as well as a rudimentary understanding of Jenkins.

This book provides a problem-solution approach to some common tasks and some uncommon tasks using Jenkins and is well-illustrated with practical code examples.

Jenkins Continuous Integration Cookbook includes problem solving and how to do recipes for many common and less common tasks. A wide range of topics are covered from integrating, securing, and maintaining Jenkins in your organization to writing your first extension.

The book begins with common maintenance tasks followed by securing Jenkins and enabling SSO. Then it explores the relationship between Jenkins builds and the Maven pom.xml. You will then learn ways to effectively communicate with various target audiences (developers, project managers, the public). You will then explore source code metrics with related recipes, and set up and run remote stress and functional tests. The book finally lists a series of 11 interesting plugins with a concluding recipe on how to create your first plugin.

Jenkins Continuous Integration Cookbook describes solutions and optimizations to problems commonly found.

Jenkins Continuous Integration Cookbook has over 90 recipes describing practical ways to use Jenkins and expanding its feature set by selective use of the best of breed plugins. Jenkins has a simple framework for writing plugins. There are over 400 plugins available. Therefore, it is easy to get lost in possibilities. Using practical recipes, this book will guide you through the complexities. The recipes are bundled into themes including security, maintainability, communication, building software, the valid use of code metrics, testing remotely, and writing your first plugin.

Read More Show Less

Product Details

  • ISBN-13: 9781849517409
  • Publisher: Packt Publishing
  • Publication date: 4/28/2012
  • Pages: 344
  • Product dimensions: 7.50 (w) x 9.25 (h) x 0.72 (d)

Meet the Author

Alan Mark Berg Bsc. MSc. PGCE, has for the last twelve years been the lead developer at the Central Computer Services at the University of Amsterdam. In his famously scarce spare time, he writes. Alan has a degree, two masters degrees, and a teaching qualification. He has also co-authored two books about Sakai (http://sakaiproject.org), a highly successful open source learning management platform used by many millions of students around the world. Alan has also won a Sakai Fellowship.

In previous incarnations, Alan was a technical writer, an Internet/Linux course writer, a product line development officer, and a teacher. He likes to get his hands dirty with the building and gluing of systems. He remains agile by ruining various development and acceptance environments.

Read More Show Less

Customer Reviews

Average Rating 4
( 1 )
Rating Distribution

5 Star

(0)

4 Star

(1)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com 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 & Noble.com 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 & Noble.com 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 BN.com 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

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com 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 BN.com. 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
  • 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

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)