Continuous Integration - PRQA Jenkins Plugin

Make it easy for developers to continuously integrate, build, and test their contributions and then visualize statuses in real time.

  • Move away from policy enforcement and towards quality
  • Get trusted results from checked-in code using known
    processing rules for reports and QA Verify snapshots.
  • Never forget to run an analysis again. And, with the help of
    QA·Verify snapshots, you can pinpoint code changes that
    cause bugs.


Continous Integration



Using Static Analysis and Continuous Integration to Ensure Code Quality


More information about the PRQA plugin is available on the Jenkins wiki.

Not using Jenkins?
If you use another tool, or you want non-standard Jenkins functionality, PRQA works with any CI tool via our comprehensive Command Line Interface (QACLI).

Stop wasting time on extended integration and testing phases

Continuous integration with the PRQA Jenkins plugin ensures code from every developer
is integrated and tested throughout the day.

The result is fewer and less serious integration errors and code that is always ready to be

Find defects early in the development process

In the traditional development process, the majority of defects are found after the development phase is complete, making it difficult to predict the quantity and severity of these defects.

This unpredictability can cause projects to extend far beyond their deadlines.

With continuous integration, defects are discovered and fixed with each commit, eliminating the need for a lengthy and unpredictable integration phase.

Spend-more-time -coding-and-less- time-integrating

Find-bugs-early-in- the- -development process

Spend more time coding and less time integrating

Continuous integration with the PRQA Jenkins plugin significantly reduces the amount of time developers spend correcting their error-ridden integrations.

When each developer continuously integrates, builds, and tests their contributions, integration errors are fixed as they occur.

Reduce the number of testing phases

A failure at any testing phase requires developers to refamiliarize themselves with the code and then rework, reintegrate, and retest it -- this wastes time.

When integration and testing occur several times throughout the development process, you are much less likely to run into major test failures that require a significant investment to fix.

Reduce-the- number-of-testing -phases

Keep-everyone- informed-of- project-status

Keep everyone informed of project status

A configurable dashboard keeps the development, product, and project managements teams informed.

The core dashboard shows the list of jobs to be done, recent test successes and failures, overall job health, build statistics, and more.

You can easily extend your dashboard’s functionality or change its look by using one of the many plugins available.

Who is this product for:

Developers and Software Architects working on large, modular software projects, who need to shorten cycles.

"RT-RK is entering the automotive industry with full force. It is evident that PRQA provides the defacto solution in this market, and we have wholeheartedly adopted QA·C.
The underlying changes to our development process are beneficial on many levels, the main one being more effective compliance with the coding rules, but also in up-skilling our engineers and streamlining our broader work-flow."