Zend - The PHP Company


Zend Blueprint for Continuous Delivery

    Zend Pattern for Continuous Integration with Jenkins

    Continuous Delivery helps companies release applications faster and with greater quality by streamlining and automating the process of bringing software from code to production. The Zend Blueprint for Continuous Delivery provides practical best practices to help companies implement each step of the continuous delivery cycle. Based on the Zend Server platform, the blueprint provides an easy way to implement these best practices through a series of patterns and plug-ins.



    Purpose of this Pattern:

    About Jenkins

    Jenkins is an open source application that monitors executions of repeated jobs, such as building a software project or jobs run by cron. Jenkins provides an easy-to-use continuous integration system, building and testing software projects continuously to make it easier for developers to integrate changes to the project. By integrating code and building upon every commit, bugs are caught faster and software projects stay in sync better across development teams.

    About the Zend Pattern

    This Zend Pattern provides a template for adding packaging and deployment to a Continuous Integration build system using Jenkins. It supports code style checks using phpcs, code violation checks using phpcpd and phpmd, and supports unit testing integration via phpunit. The last step packages the application in a *.zpk deployment package and deploys the archive onto Zend Server. Note that Phing is required on the build server for this pattern.

    Why Use the Zend Pattern?

    Continuous delivery requires that code must be deployable at all times, in addition to ensuring that it builds successfully and passes all unit tests. When used with Jenkins, Zend Server's deployment automation validates that, after every integration, applications and code libraries can be rapidly and consistently deployed onto QA, staging, or production servers.

    Included in this Pattern:

    • Jenkins implementation guide

    Getting Started:

    Download the implementation guide and follow the best practices contained therein

    Resources
    WHITE PAPER

    Zend Continuous Delivery Blueprint

    more»

    DATASHEET

    Continuous Delivery Solution Sheet

    more»

    DATASHEET

    Continuous Delivery Assessment

    more»

    Customer Quote

       We were able to implement Continuous Integration with Hudson and tie it into Maven, using the Zend SDK to create packaged applications for robust deployment using Zend Server. As a result, we’re now catching bugs before they make it to QA and pushing out new releases twice a week with much higher confidence.   

    Jon MarstonVP of Engineering at English Central

       Jenkins has always been an essential tool for Novadex, but deployment is not one of its native components. This means that before using Zend Server, we had to resort to creating our own scripting and packaging mechanisms for the deployment of our code. Leveraging Zend Server’s capabilities and SDK allowed this scripting to be simplified and to effortlessly support server clusters, enabling non-expert users to initiate deployments, while providing extra control and the flexibility essential for Novadex to stay at the forefront of cloud-based business communication management.   

    Andreas RossbachChief Technology Officer at Novadex