Integrating RVS with Jenkins
I've recently been integrating RVS with Jenkins. In this post, I'll show how this will help you track your RVS results over time if you use Jenkins to run continuous builds of your code.
I'll use an example project that collects structural coverage data from unit tests (using the RVS tools RapiCover and RapiTest).
It's easy to set up the RVS integration with a configuration plugin; simply point to your RVS project file and set up the rvsdriver commands to run your integration (Figure 1).
Figure 1. Setting up a build
Now, every time Jenkins builds your code, RVS analyzes it to produce a report, and also tracks the progress of your testing over time (Figure 2). While this example project collects unit test and structural coverage data, execution time data is also supported.
Figure 2. Trends in unit test and structural coverage results over time
You can open the report from individual builds for more information, for example detailed test or coverage results (Figure 3).
Figure 3. Detailed coverage results from a build
We've also been integrating RVS with Jenkins pipelines, including Blue Ocean visual pipelines. Full support for Jenkins will be available in the next version of RVS, 3.8. If you want to know more about RVS, contact us or request a trial.
This work was part of the AMASS project.
White papers & webinars
Want to learn about common challenges and solutions in critical software verification? Our white papers and webinars may be just the thing:
- Multicore Timing Analysis for DO-178C
- Eight top code coverage questions in embedded avionics systems
- Seven Roadblocks to 100% structural coverage (and how to avoid them)
- Automating WCET Analysis for DO-178B & DO-178C
- Three steps to avoid software obsolescence in avionic systems
- CodeTEST® Replacement with RVS
- Multicore Timing Analysis for DO178 Projects Webinar
- Multicore for ISO 26262 Webinar