Continuous Integration

Slider
QA Systems > Tools > qa-c/ > Continuous Integration

What is Continuous Integration

 

Continuous Integration is a principle that encourages developers and teams to share and integrate all their contributions continuously – literally.

  • Moving away from the concept of nightly builds and instead embracing the concept of continuous builds
  • Moving away for policy enforcement and instead rely on quality enforcement

And the objective is to gain full – and automated – control of your software verification and software dependencies, so that every single developer commit has the potential of being a release candidate.

You can run our static testing tools on the command line so that they are easily integrated with many CI tools.

Jenkins plugin

 

Jenkins CI defines jobs on the master that are executed automatically on the slaves typically when changes are delivered to the SCM system. The result of each build is presented on the web as well as statistical information over time. Using different plug-ins, the jobs can be configured to do anything that can be automated.

The ‘early and often’ approach that we advocate for our static analysis solutions clearly resonates with the Continuous Integration philosophy that is increasingly being adopted as a robust approach to software quality.

The Jenkins plugin will allow you to automate the analysis of enabled C and C++ projects, enabling you to perform the analysis as a part of your Continuous Integration process.

The plugin offers a range of functionality, including:

 

  • Displaying a graphical history depicting the number of messages, and overall compliance levels in your project
  • Marking a build as unstable if the number of messages exceeds a threshold
  • Producing and archiving Compliance Reports
  • Allowing analysis results to be uploaded to QA-Verify
BACK TO QA-C/QA-C++