Bergmann - Integrating PHP Projects with Jenkins
Here you can read online Bergmann - Integrating PHP Projects with Jenkins full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Sebastopol;Calif, year: 2011, publisher: OReilly Media, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
Integrating PHP Projects with Jenkins: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Integrating PHP Projects with Jenkins" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Todays web applications require frequent updates, not just by adding or upgrading features, but by maintaining and improving the softwares existing code base as well. This concise book shows PHP developers how to use Jenkins, the popular continuous integration server, to monitor various aspects of software quality throughout a projects lifecycle.
Youll learn how to implement continuous integration to automate processes for building and deploying regular software releases. The book also shows you how to use Jenkins to monitor and improve your application through continuous inspection. Youll come to understand why reducing complexity and eliminating duplicate code is just as important as introducing new functionality.
- Create a job for your PHP project in Jenkins and set up a continuous integration environment
- Add static code analysis tools to your build for continuous inspection
- Use specialized...
Bergmann: author's other books
Who wrote Integrating PHP Projects with Jenkins? Find out the surname, the name of the author of the book and a list of all author's works by series.
Integrating PHP Projects with Jenkins — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Integrating PHP Projects with Jenkins" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
Copyright 2011 Sebastian Bergmann
OReilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (.
Nutshell Handbook, the Nutshell Handbook logo, and the OReilly logo are registered trademarks of OReilly Media, Inc. Integrating PHP Projects with Jenkins , the image of starlings, and related trade dress are trademarks of OReilly Media, Inc.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and OReilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps.
While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
for more information on this offer!
Please note that upgrade offers are not available from sample content.
Most web applications are changed and adapted frequently and quickly. Their environment, for example the size and the behaviour of the user base, are constantly changing. What was sufficient yesterday can be insufficient today. Especially in a web environment it is important to monitor and continuously improve the software quality not only when developing, but also when maintaining the software. The practice of Continuous Integration is the solution of choice to achieve this goal.
Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least dailyleading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. |
| -- Martin Fowler |
Continuous Integration reduces the amount of repetitive processes the developers need to perform when building or deploying the software thus reducing the risks of late discovery of defects, producing low-quality software, lack of project visibility as well as lack of deployable software.
At least as far as I know, Sebastian Nohn was the first to experiment with the continuous integration of PHP projects. Back in 2006 he described on his blog how to use Apache Ant and CruiseControl to set up a continuous build that invoked PHPUnit to run the unit tests of a PHP project.
Soon thereafter, the developers of Mayflower GmbH started to build a quality assurance platform for PHP projects that was based on CruiseControl. It not only ran unit tests as part of the build loop but also static code analysis tools such as PHP_CodeSniffer to collect software metrics over time.
This quality assurance platform gave Manuel Pichler the idea to start the phpUnderControl open source project. This was a set of patches for CruiseControl (which could not be customized or extended through plugins) that added out-of-the-box support for PHP projects. phpUnderControl significantly lowered the barrier to entry for introducing continuous integration into a PHP project but since it was based on CruiseControl it was a nightmare from an operations point of view and not as customizable and flexible as one would like.
The developers of Mayflower GmbH later refactored their quality assurance platform for PHP projects into a tool that can be used with arbitrary continuous integration servers. It was open-sourced under the name PHP_CodeBrowser.
When the Java community started to migrate from CruiseControl to more modern continuous integration servers, I had a look at Hudson (as Jenkins was called back then) and tried it together with the PHP quality assurance toolchain. I was pleasantly surprised to find a product that was not only more convenient to use and more robust (from an operations perspective) than CruiseControl but to also meet a vibrant development community. Thanks to the plethora of plugins developed and maintained by this community, Jenkins supports building and testing virtually any project, including PHP projects.
The PHP community has developed a wide range of quality assurance tools since 2006. Where Sebastian Nohn only ran PHPUnit tests with Apache Ant and CruiseControl, a typical continuous integration setup for a PHP project today also includes the detection of violations of a defined set of coding guidelines and the gathering of various software metrics as well as the generation of API documentation, for instance.
Over the course of the last two years I have successfully set up continuous integration environments that are based on Jenkins for our customers. These development teams leverage Jenkins to monitor the various aspects of software quality throughout the lifecycle of their projects. This enables them to create, maintain and extend sustainable software of high quality with PHP. The result of this experience is a template for Jenkins jobs for PHP projects that I have released as an open source project.
This book covers everything you need to know in order to use Jenkins for the continuous integration of your PHP projects. Here is how the book is organized:
In this chapter you will learn how to use Apache Ant to automate your build.
This chapter explains how to set up Jenkins and install the PHP tools that are required to continuously integrate a PHP project.
This chapter shows how to create a job for a PHP project in Jenkins.
Building on the continuous integration environment that was set up in the previous chapter, you will learn in this chapter how to add static code analysis tools to the build for continuous inspection.
This chapter shows how the automated build and continuous integration of a PHP project can be simplified by using the PHP Project Wizard and the Template for Jenkins Jobs for PHP Projects .
This chapter concludes the book with a summary of the benefits of Continuous Integration and Continuous Inspection while providing an outlook of what you can implement in addition to the processes and techniques described in this book.
This book makes the assumption that the reader is familiar with the concept of Continuous Integration and the set of problems it aims to solve. [] are recommended basic and further reading, respectively, on this topic.
While this book explains how to install Jenkins and how to configure it for PHP jobs it does not cover topics such as authentication, for instance, that are impartial to the programming stack used. Furthermore, the assumption is made that Jenkins is installed in a UNIX environment. For Jenkins-related topics not covered in this book the reader is referred to [].
The planning, execution, and automation of tests for the different layers and tiers of a PHP-based web application is also outside the scope of this book. [] is an excellent resource on these matters.
If you would like to find out more about Jenkins and PHP, and to get the latest updates, visit this book's companion website at http://jenkins-php.org/. This is also where the template for Jenkins jobs for PHP projects is maintained.
Font size:
Interval:
Bookmark:
Similar books «Integrating PHP Projects with Jenkins»
Look at similar books to Integrating PHP Projects with Jenkins. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book Integrating PHP Projects with Jenkins and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.