CI/CD pipeline

Technique

A CI/CD pipeline was used as part of the functional verification infrastructure for a RISC-V vector accelerator, automating constrained-random test generation, simulation, error reporting, regression execution, and coverage collection. In the reported project, the CI infrastructure was built with Jenkins, used RISCV-DV to generate random binaries, integrated with GitLab for version control, issue tracking, and documentation, and contributed to finding 3005 errors and reaching 95.79% functional coverage.

First seen 5/27/2026

Last seen 5/27/2026

Evidence 4 chunks

Wiki v1

WIKI

Overview

In the RISC-V vector accelerator verification project described in Functional Verification of a RISC-V Vector Accelerator, the CI/CD pipeline was part of a broader verification infrastructure that included a UVM environment, Spike-based co-simulation, assertions, coverage, constrained-random binary generation, simulation, and automated error reporting. The paper states that this CI/CD infrastructure played an essential role in code health, maintainability, and coverage closure, and that the overall process found 3005 errors and reached 95.79% functional coverage.

Role in the verification flow

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

4 connections

Functional Verification of a RISC-V Vector Accelerator ← uses 97% 2e

The paper describes a CI/CD infrastructure using Jenkins for running regression tests.

Jenkins uses → 97% 1e

The CI/CD pipeline is implemented using Jenkins as the CI server.

GitLab uses → 92% 1e

The CI/CD pipeline uses GitLab for version control and issue tracking.

riscv-dv uses → 95% 1e

The CI pipeline generates random tests using RISCV-DV as part of its workflow.

LINKED ENTITIES

4 links

Functional Verification of a RISC-V Vector Accelerator USES Extracted graph relationship

Jenkins USES Extracted graph relationship

GitLab USES Extracted graph relationship

riscv-dv USES Extracted graph relationship

CITATIONS

9 sources

9 citations — click to expand

[1] The CI/CD pipeline was part of the verification infrastructure for a RISC-V vector accelerator and supported automated constrained-random test generation, simulation, and error reporting. Functional Verification of a RISC-V Vector Accelerator

[2] The CI/CD infrastructure contributed to code health, maintainability, coverage closure, finding 3005 errors, and reaching 95.79% functional coverage. Functional Verification of a RISC-V Vector Accelerator

[3] CI pipelines allowed the RTL design and verification teams to test new features and find new errors, and regressions were run before changes could be merged after fixes. Functional Verification of a RISC-V Vector Accelerator

[4] Continuous integration simulations were used to generate and run tests and collect coverage metrics, including functional coverage, assertion usage, and code coverage. Functional Verification of a RISC-V Vector Accelerator

[5] The CI infrastructure was built using Jenkins. Functional Verification of a RISC-V Vector Accelerator

[6] GitLab was used for version control, issue tracking, and Wiki-based documentation for running simulations. Functional Verification of a RISC-V Vector Accelerator

[7] The New tests pipeline generated random tests with RISCV-DV, compiled the DUT, executed binaries, classified tests, and used passing tests for regression creation. Functional Verification of a RISC-V Vector Accelerator

[8] The Retry, Selection, and Regressions pipelines re-executed failed tests on main-branch changes, selected coverage-ranked regression sets daily, ran small regressions for merge candidates, and ran large regressions weekly. Functional Verification of a RISC-V Vector Accelerator

[9] Nightly testing ran 24 tests per night between April and July and 50 tests per night between August and late November, with about 500 vector instructions per test. Functional Verification of a RISC-V Vector Accelerator