Automated / CI

Continuous Integration was first proposed by Grady Booch in 1991 as part of his Booch Method for software development which was a forerunner of UML (Universal Modelling Language). Continuous Integration mandates that all developers check-in, or merge, their working copies of source code to the main development code base on a regular basis, usually several times a day. Once a code check-in occurs, an automated process tests that the code changes haven’t adversely affected the compilation of the software.

Each of the software test tools available from SDC Systems solution providers can be integrated with a range of  Continuous Integration tools such as Atlassian Bamboo, Hudson, TeamCity and Microsoft Team Foundation Server, however, Jenkins being available as open source software has been adopted heavily across all industries.

Continuous Integration with Jenkins

Jenkins LogoJenkins is an open source automation server, written in Java, to help automate the non-human part of the whole software development process, with now common things like continuous integration, but by further empowering teams to implement the technical part of a Continuous Delivery.

Jenkins is a server-based system supporting software configuration management (SCM) tools including AccuRev, Subversion, Git, Mercurial, Perforce, Clearcase and RTC, and can execute Apache Ant and Apache Maven based projects as well as arbitrary shell scripts and Windows batch commands.

Enhancing Jenkins Capabilities

The Klocwork static analysis tools can be integrated into your Jenkins workflow either to provide defect and metric information on key milestone builds or by performing a diff based analysis of each code check-in as it occurs.  The analysis performed by Jenkins uses the same analysis engine and checker definitions that your developers use on the desktop giving an end-to-end static analysis solution.  More details…

Using either the results from static analysis or its own internal code analyser, the software architecture tools from Lattix add an additional level of understanding of your code highlighting deviations from your initial architectural design.  With code reuse becoming an ever more significant part of software development it is essential to make sure that any code changes that break the APIs of libraries or add additional dependencies are caught and resolved. More details…

While your Jenkins project is executing your test scripts either developed in-house, using open source solutions such as Google Test and cppunit or commercial test frameworks, Squish Coco from froglogic can provide code coverage and other metrics relating to your source code and test regime.  Squish Coco supports statement, branch and MC/DC coverage. More details…

If your application software makes use of open source software then analysis of security vulnerabilities and license compliance, using FlexNet Code Insight, can be added to your Jenkins job to easily catch new packages that get added and to report on issues that will have a negative impact on your application. More details…

Find out more…

For more information on how to add static code analysis, architecture analysis, code coverage, open source security vulnerability or open source license compliance to your Continuous Integration process please complete the form below.

Full Name (required):

Company Name (required):

Your Email (required)