Jenkins

Tool

Jenkins is an open-source CI server and automation server. In the provided RISC-V vector accelerator verification evidence, Jenkins is the basis of a CI infrastructure that generates and runs tests, records coverage metrics, retries failed tests, selects regression suites by coverage, and runs merge-gate and weekly regressions.

First seen 5/27/2026

Last seen 6/1/2026

Evidence 2 chunks

Wiki v2

WIKI

Overview

Jenkins is described in the evidence as an open-source CI server. Its public upstream repository describes it as the “Jenkins automation server” and identifies the implementation language as Java. [jenkins-public-repo] [jenkins-ci-server]

Role in the RISC-V vector accelerator 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 99% 3e

Jenkins is used as the CI server for running verification pipelines.

CI/CD Infrastructure ← uses 97% 1e

Jenkins is used as the CI server to implement the CI/CD infrastructure.

CI/CD pipeline ← uses 97% 1e

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

CI/CD Infrastructure implements → 99% 1e

Jenkins is the CI server used to implement the CI/CD infrastructure

LINKED ENTITIES

2 links

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

CI/CD Infrastructure IMPLEMENTS Extracted graph relationship

CITATIONS

8 sources

8 citations — click to expand

[1] Jenkins public repository describes it as the Jenkins automation server and identifies Java as the repository language. jenkinsci/jenkins

[2] The verification infrastructure was built using the open-source CI server Jenkins, with a set of interacting pipelines. Functional Verification of a RISC-V Vector Accelerator

[3] The CI flow generated and ran tests and collected functional coverage, assertion usage, and code coverage metrics from simulations. Functional Verification of a RISC-V Vector Accelerator

[4] The Jenkins infrastructure implemented four pipelines: New tests, Retry, Selection, and Regressions. Functional Verification of a RISC-V Vector Accelerator

[5] The New tests pipeline generated random tests with RISCV-DV, compiled the DUT, executed binaries, and classified tests as passed or failed. Functional Verification of a RISC-V Vector Accelerator

[6] The Retry pipeline re-executed failed tests for each change in the main branch of the DUT repository and reclassified them. Functional Verification of a RISC-V Vector Accelerator

[7] The Selection pipeline ran daily at midnight, ranked passed tests by collected coverage when a threshold was met, and created large and small regression sets. Functional Verification of a RISC-V Vector Accelerator

[8] The Regressions pipeline ran the small regression set for candidate DUT changes and the large regression set weekly to check that recent changes did not break known-good tests. Functional Verification of a RISC-V Vector Accelerator