In This Chapter
Continuous integration and continuous builds are mainstay features of modern software factories.
Continuous integration is the practice of development changes being tested, built, and reported in small increments during the development process. Continuous build is an extension of this practice to provide a newly tested build of the software every time a developer commits changes.
Understanding continuous integration principles, in conjunction with continuous build tools, helps drive an efficient software factory, and by extension, efficient software development. These principles include:
With these principles in mind, the developer's role in the continuous integration process can be summarized as follows. Developers should:
Software tools can help with managing and practising continuous integration; in fact, continuous builds are normally vastly software driven. Software considerations include:
There are many different choices for continuous build software available, such as Jenkins, CruiseControl, Continuum, Bamboo, and others.
This tutorial shows how to use Jenkins for the task at hand.
In regards to Servoy projects, Jenkins is used to fill the following needs in our software factory
Jenkins is very flexible in how they can be configured and the methods and strategies can differ depending on a variety of factors. In the case of using it with Servoy, we also utilize it's ability to run ANT scripts. Through these ANT scripts, tools provided by Servoy Developer export the solution into .servoy (for unit tests) and .war (for deployment and mobile unit tests) formats, then ant runs the unit test tools provided by Servoy: a smart client based test client that will import the solution into a repository and run unit tests on it and a mobile client based test client that will import the service solution and deploy the mobile test war and run unit tests on it . Finally, if unit tests are passed, end-to-end tests are run (using a war deployment of the solutions and ngclient + protractor and/or selenium runner for java) and then a war is deployed to a manual test Tomcat server.
Rather than explain everything in detail that can be done with Jenkins and a Servoy project, it is more beneficial to provide an example of Jenkins and the supporting applications configured for a continuous build server.
The Servoy Software Factory Example using Jenkins section will cover in detail setting up a continuous build server for some sample Servoy solutions.