Jenkins: The Definitive Guide: Continuous Integration for the Masses

If you have an agile team, if you do automated testing, if you use git or subversion, if you need to share code, if you work in software, or are an IT Girl, or an IT Guy, this book is a must buy. Jenkins is the most awesome, free, flexible, productivity enhancing thing in the world. Free to download. Free to use, IF you can use it. However, you could waste boatloads of money with this free tool if you don't know what you are doing. Let me break down for you what usually happens at a company when an "Agile Transition" comes along. 1. Hire consultant who sets up awesome demo. Consultant says, "Here! It's Easy! Sets up Jenkins, shows you beautiful result using 7 different programming languages, Git, which your team may not use, and integrates it for you in a tool you don't own but that's ok because you are on the trial version. 2. Contract ends, and Consultant who set up whiteboard is no longer there. Your trial version runs out, or your Jenkins server goes down, and now you have NO ONE who knows what the heck is going on. 3. You panic. Try the backup. Find out it wasn't part of the demo setup. In fact, the demo isn't even likely set up for multiple users correctly! Your new tool you decided to go with isn't integrated with it. However, having had a taste of the awesome sauce that is a build on demand, no one wants to LIVE without their CI system (Jenkins build). That is when you should buy this book. Why? Because everything you need is mostly already made and you don't have to manually remake it, but these guys are the guys who've DONE this stuff. They are the gurus you want to take advice from. Also, there is very minimal bullshennanigans in this book. I rarely fell asleep, and for a technical book that is high praise. So anyways, if you can't hire these guys are get the consultant who set this up in the first place, this book will help you. Anyhow, it helped me, and now I'm a Jenkins addict trolling for new plug-ins at all hours of the night. If you don't know when Jenkins is, don't bother buying this book. If you don't understand this review, likely the book isn't for you.

This book was a quick read and gives a fairly good understanding of the more popular plugins and setup for a Jenkins CI server(s). The book covered 90% continuous integration for maven/java projects, so be aware of that if you are planning to use other build tools/programming languages for your projects( the book does cursorily touch on using php and ruby but it's by no means definitive). That said, Jenkins isn't a difficult service to understand and book outlined as such in a concise way. I would recommend this book for someone who has no experience with Jenkins and would prefer an organized alternative to reading the online documentation. I won't give it 5 stars, however, because it's not a definitive book about Jenkins, but more beginning guide to integrate a Jenkins setup for your organizational needs.

This book is now 7 years old, so expect to find some dated info. You can work through the issues by Googling it. Does a good job of explaining the concepts. Good intro to Jenkins if you've never played with it before.

This book is a great resource for all levels of developers that utilize Jenkins. The book is not the end to end 'Bible' for Jenkins but it's a great resource that explains pretty much all the essential building blocks. I've read the book a couple times now and I have realized that I overlooked features for didn't fully grasp how powerful they were originally. It's also wonderful to resource to help train others team members. We keep a couple copies around the office now.

This is an excellent book for beginners who are seriously looking to get started with Jenkins. I just found some of the screenshots were too light or almost illegible with very small font size - but then that is a common problem with O'Reilly books and one should be fine if they try out the options hands-on the computer with the book by their side.

I liked this book. It helped to create a CI using Jenkins.But some points of the book the author does not explain very well how to do, only explain, but does not show how to implement. So, I had to search in internet and understand. But in general I recommend this book if you want to work with jenkins and create continuous integration.

Might work for getting an idea of what Jenkins does. However, many users will likely be interested in configuring jenkinsfile, which is not mentioned at all in this book.

I used to use Hudson without reading anything about the product, just click, click, and UI obvious configuration. I decided to migrate to Jenkins and started reading this book. Wow! I figure out a lot of new things (specially some very good plugins) that helped me on my builds. Again, even if you already have an running CI solution this book can give you some cool ideas.

Il prodotto è così semplice da usare che quasi non serve un manuale. L'ho comprato per approfondire e sfruttarlo al meglio, ma alla fine ho trovato tutte informazioni ampiemente disponibili sul web.

As I wish, a quick delivery and good product as requested. Well done job, always I will use and recommend this seller.

Das Buch ist ein guter Einstieg, kann aber nicht Stand Alone genutzt werden. Der Autor kann sich nicht entscheiden zwischen einer step by step Anleitung und einer Übersicht. So gelingt bei weitem nicht jedes Beispiel und die besprochene Kombination von Tools (Maven, Git, Cobertura, ...) bleibt oft Stückwerk. Am Ende muss man doch in die Einzeltools rein. Dennoch: wie gesagt, ein passabler Einstieg.

Il s'agit d'une référence sur Jenkins mais également sur l’Intégration Continue. C'est un très bon support pour découvrir et mettre en oeuvre une démarche d’intégration continue

Jenkins has become a staple of many software development toolsets, especially those pushing into the Continuous Integration/Continuous Deployment model. As part of that methodology, Jenkins plays a major role in deployment of a build using automated scripts. While I've worked with other tools (including Hudson, the predecessor of Jenkins, as well as Chef), playing around with Jenkins in the early days showed what it was capable of. This book is intended for those who need to set up a Jenkins deployment system and use it. The introduction to the subject is gentle enough for even inexperienced developers or administrators, although coding and system experience i definitely a bonus. Working through the book, for the most part, my knowledge of Jenkins grew considerably and me already familiar pieces became fleshed out. The book is well written and well laid out. It is easy to find what you need, and the instructions are sufficient that you won't end up having to dig around the Web for alternate explanations. There's a lot of content here, but most people won't need all of it. But what you do need is here, and clearly explained. Recommended!