Merge pull request #2477 from NVIDIA/bump-toolkit-1.19.1-olm #3247
tariq1890ci.yaml
on: push
variables
/
variables
7s
golang-checks
/
go-check
3m 31s
golang-checks
/
unit tests
38s
golang-checks
/
go-build
1m 45s
config-checks
/
helm-lint
9s
config-checks
/
validate-csv
35s
config-checks
/
validate-helm-values
36s
code-scanning
/
Analyze Go code with CodeQL
4m 21s
coverage
/
coverage
1m 53s
image-builds
/
build-gpu-operator-arm64
2m 21s
image-builds
/
build-gpu-operator-amd64
2m 29s
e2e-tests
/
e2e-tests-containerd
51m 54s
e2e-tests
/
e2e-tests-nvidiadriver
31m 37s
release
/
push-gpu-operator-bundle-image
19s
Annotations
5 warnings and 10 notices
|
golang-checks / unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
golang-checks / go-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
coverage / coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
image-builds / build-gpu-operator-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
image-builds / build-gpu-operator-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
variables / variables
Operator image: ghcr.io/nvidia/gpu-operator:2f5457b4
|
|
variables / variables
Push on build: true
|
|
variables / variables
Commit SHA: 2f5457b4
|
|
image-builds / variables
Multi-arch image: ghcr.io/nvidia/gpu-operator:2f5457b4
|
|
image-builds / variables
Push on build: true
|
|
image-builds / variables
Commit SHA: 2f5457b4
|
|
e2e-tests / variables / variables
Operator image: ghcr.io/nvidia/gpu-operator:2f5457b4
|
|
e2e-tests / variables / variables
Push on build: true
|
|
e2e-tests / variables / variables
Commit SHA: 2f5457b4
|
|
release / variables
Releasing: ghcr.io/nvidia/gpu-operator:2f5457b4 → ghcr.io/nvidia/gpu-operator:main-latest
|