This document describes the pipelines available to the developers and code
maintainers in the Jenkins server. Note
that pipelines with the suffix *-Private
are only available to code
maintainers and The OpenROAD Project members as they can contain confidential
information. Thus, to access Private pipelines one needs to have authorization
to access confidential data and be logged in the Jenkins website.
Below there is a list of the available features. Instructions on how to navigate Jenkins to access these features are available here.
- Find your build through Jenkins website or from GitHub.
- See test status: Pass/Fail.
- Log files for each test.
- Build artifacts to reproduce failures.
- HTML reports about code coverage and metrics.
- OpenROAD-Coverage-Public
- Description: run dynamic code coverage tool
lconv
. - Target: master branch.
- Report link here.
- Description: run dynamic code coverage tool
- OpenROAD-Coverity-Public
- Description: compile and submit builds to Coverity static code analysis tool.
- Target: master branch.
- Report link here.
- OpenROAD-Nightly-Public
- Description:
openroad
unit tests, docker builds, ISPD 2018 and 2019 benchmarks for DRT and large unit tests of GPL. - Target: master branch.
- Description:
- OpenROAD-Public
- Description:
openroad
unit tests and docker builds. - Target: all branches and open PRs.
- Description:
- OpenROAD-Special-Private
- Description: for developer testing, runs ISPD 2018 and 2019 benchmarks for DRT and large unit tests of GPL.
- Target branches:
TR_*
,secure-TR_*
,TR-*
,secure-TR-*
.
- OpenROAD-Private
- Description:
openroad
unit tests and docker builds. - Target: all branches. Note that PRs will be run on public side after "Ready to Sync Public" workflow.
- Description:
- Information about OpenROAD Flow CI jobs can be found here