NVIDIA / gpu-operator / 38969390420
45%
main: 45%

LAST BUILD BRANCH: pull-request/3089
DEFAULT BRANCH: main
Ran
Jobs 1
Files 75
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 45.004%. First build
38969390420

push

github

abrarshivani 
ci: record each complete main build and test only those

The daily workflow publishes the main chart and the main OLM bundle in
two independent jobs, so a night can end with one of them published and
the other missing. Forward compatibility picked the newest chart tag on
its own and had no way to tell whether that night's build was whole.

Add a record-main-build job that runs only after both publish jobs
succeed. It resolves the digests of the published chart and bundle, the
operator image and every operand image in values-overrides.yaml, and
pushes a small JSON record of them, together with the main version,
source commit and run URL, as an OCI artifact to
ghcr.io/<owner>/gpu-operator/main-builds:<main version>. A record with
that tag therefore means the chart and bundle for that version were both
published. A failure of this job is reported to Slack like the others.

Forward compatibility now lists the main-builds tags instead of the
chart tags, keeps the same version pattern and freshness check, and
refuses to run when the chart tag no longer has the digest the record
captured. The script is renamed to get-latest-main-build.sh, and the age
limit to MAIN_BUILD_MAX_AGE_HOURS, to match. Both workflows log regctl in
to ghcr.io with the workflow token, so reading the records does not depend
on the visibility the organization gives the new package.

Signed-off-by: Abrar Shivani <ashivani@nvidia.com>

5864 of 13030 relevant lines covered (45.0%)

0.45 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38969390420.1 75
45.0
GitHub Action Run
Source Files on build 38969390420