Skip to content

Fix CI: add scan retry and update deprecated GitHub Actions #318

Fix CI: add scan retry and update deprecated GitHub Actions

Fix CI: add scan retry and update deprecated GitHub Actions #318

Triggered via push May 11, 2026 13:53
Status Success
Total duration 13m 43s
Artifacts 18

docker.yml

on: push
get-version
7s
get-version
paths-filter
9s
paths-filter
build-baseimage-amd64
29s
build-baseimage-amd64
build-baseimage-arm64
38s
build-baseimage-arm64
build-core-amd64
2m 30s
build-core-amd64
build-core-arm64
1m 43s
build-core-arm64
create-manifest-baseimage
12s
create-manifest-baseimage
build-assemble-amd64
3m 13s
build-assemble-amd64
build-classify-amd64
3m 9s
build-classify-amd64
build-mega-amd64
4m 4s
build-mega-amd64
build-phylo-amd64
3m 3s
build-phylo-amd64
create-manifest-core
45s
create-manifest-core
build-assemble-arm64
3m 28s
build-assemble-arm64
build-classify-arm64
2m 56s
build-classify-arm64
build-mega-arm64
4m 38s
build-mega-arm64
build-phylo-arm64
3m 30s
build-phylo-arm64
Matrix: scan-containers
test-core
3m 9s
test-core
test-core-arm64
0s
test-core-arm64
create-manifest-assemble
43s
create-manifest-assemble
create-manifest-classify
1m 51s
create-manifest-classify
create-manifest-mega
1m 37s
create-manifest-mega
create-manifest-phylo
1m 15s
create-manifest-phylo
test-assemble
2m 19s
test-assemble
test-assemble-arm64
0s
test-assemble-arm64
test-classify
2m 17s
test-classify
test-classify-arm64
0s
test-classify-arm64
test-phylo
2m 14s
test-phylo
test-phylo-arm64
test-phylo-arm64
all-tests-pass
2s
all-tests-pass
Matrix: deploy-to-quay
Fit to window
Zoom out
Zoom in

Annotations

15 warnings and 6 notices
paths-filter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. 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/
build-baseimage-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
build-baseimage-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
build-core-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
build-core-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
build-classify-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
build-assemble-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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 should be defined before their use: docker/Dockerfile.assemble#L23
UndefinedVar: Usage of undefined variable '$PERL5LIB' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
build-phylo-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
build-classify-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
build-phylo-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
build-assemble-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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 should be defined before their use: docker/Dockerfile.assemble#L23
UndefinedVar: Usage of undefined variable '$PERL5LIB' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
build-mega-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
build-mega-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
scan-containers (baseimage)
Trivy found 0 findings for baseimage (after policy filtering)
scan-containers (core)
Trivy found 0 findings for core (after policy filtering)
scan-containers (assemble)
Trivy found 0 findings for assemble (after policy filtering)
scan-containers (phylo)
Trivy found 0 findings for phylo (after policy filtering)
scan-containers (classify)
Trivy found 0 findings for classify (after policy filtering)
scan-containers (mega)
Trivy found 0 findings for mega (after policy filtering)

Artifacts

Produced during runtime
Name Size Digest
broadinstitute~viral-ngs~9F1LZS.dockerbuild
107 KB
sha256:a098a49fad0ff6331b23836ad8cc10cdafdaa50467b4954312917ca7fba68c7c
broadinstitute~viral-ngs~B3FB8I.dockerbuild
45 KB
sha256:643b97edca8eba31369741c9d0de17d6b5b685ffa3d5f3df54fce41b396a9132
broadinstitute~viral-ngs~KWF3LP.dockerbuild
77.4 KB
sha256:0d80932fda7dc72865cfcea7e17475b836f683d6644939b6436d91da9fe71bed
broadinstitute~viral-ngs~MRCOXO.dockerbuild
119 KB
sha256:08909d0845116ccc308c8b21b9297a49111bbcbbfd4c25e5ccf87c387cf5caab
broadinstitute~viral-ngs~NB9V3R.dockerbuild
107 KB
sha256:f982ae7767585d3efdf9d36648750ffe312bd90f6b19ee057615ba543ae52144
broadinstitute~viral-ngs~NOY3VE.dockerbuild
112 KB
sha256:52ba2ecae7bdeb49d7382406d154c975943ceed91beeb78ed8adf753bd67d010
broadinstitute~viral-ngs~OLRVEK.dockerbuild
115 KB
sha256:87fb2b0af25216198bd44e763c0efea1cc0793b5194e63f95a24c022b8b3a9e1
broadinstitute~viral-ngs~OM0NEC.dockerbuild
105 KB
sha256:681db4bb2329bfe503bec881af1ad2e08da087132e4af584a16c7545eae9dcf6
broadinstitute~viral-ngs~QPVAY1.dockerbuild
107 KB
sha256:7975a50d75db10964f73f4dd98447c1ebc095848b92e8db566c2c9c613301532
broadinstitute~viral-ngs~W9M0J7.dockerbuild
41.8 KB
sha256:7fd07bfc13682d3d413c14a3064990f6177b69e247f0244dc4e8152eee1d9a34
broadinstitute~viral-ngs~WCLWVV.dockerbuild
79.2 KB
sha256:dd4249268954f37dbbdcf37f127af01ae2e2bb93737c1615d01b96f7b3efb62f
broadinstitute~viral-ngs~ZA8MEQ.dockerbuild
101 KB
sha256:dfd4e718d569b555662984e1ec2b024feb99ef6cad534cddb0cc14628aeb3954
trivy-assemble
79.7 KB
sha256:10d34dacfb71b9ce1bc400cc306a26779c14b953bf2c587ba8feed575d3203f9
trivy-baseimage
69.4 KB
sha256:6c123b7152b99484ff491d8f7e2e642bccd9cd4b1c83c983b1186d3de4404be8
trivy-classify
79.6 KB
sha256:59c8ad6ad5d10820e5be99cf2e54b804e90f6f6a9cd03dd859f392620ff421d4
trivy-core
75.2 KB
sha256:21fb67169eaceba2d7a9f71de9fa7dfe232023ecbfbde479c14e82def5298dde
trivy-mega
84.5 KB
sha256:7eb28ad3272297418b0ae21f23662400789b11d7e19250d8b275f50ad5638b28
trivy-phylo
80.5 KB
sha256:75ed8e9b3849d9bb9638dceda14a0f954149322645213ce00a6bffbbb763a1d5