Skip to content

ARM64 builds in Chroot - Ubuntu AZL eLxr #462

ARM64 builds in Chroot - Ubuntu AZL eLxr

ARM64 builds in Chroot - Ubuntu AZL eLxr #462

Triggered via pull request April 21, 2026 22:31
Status Success
Total duration 2m 6s
Artifacts 4

pre-merge.yml

on: pull_request
pre-merge  /  sanitize-project-folder
3s
pre-merge / sanitize-project-folder
pre-merge  /  license-compliance-check
0s
pre-merge / license-compliance-check
pre-merge  /  run-repo-pipelines
1m 42s
pre-merge / run-repo-pipelines
pre-merge  /  zizmor-scan
9s
pre-merge / zizmor-scan
pre-merge  /  secrets-gitleaks-scan
16s
pre-merge / secrets-gitleaks-scan
pre-merge  /  trivy-filesystem-scan
17s
pre-merge / trivy-filesystem-scan
pre-merge  /  trivy-critical-scan
18s
pre-merge / trivy-critical-scan
pre-merge  /  trivy-config-scan
9s
pre-merge / trivy-config-scan
pre-merge  /  bandit
13s
pre-merge / bandit
Matrix: pre-merge / Scan Docker Images for CIS
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
pre-merge / zizmor-scan
No file matched to [/home/runner/work/image-composer-tool/image-composer-tool/**/*requirements*.txt,/home/runner/work/image-composer-tool/image-composer-tool/**/*requirements*.in,/home/runner/work/image-composer-tool/image-composer-tool/**/*constraints*.txt,/home/runner/work/image-composer-tool/image-composer-tool/**/*constraints*.in,/home/runner/work/image-composer-tool/image-composer-tool/**/pyproject.toml,/home/runner/work/image-composer-tool/image-composer-tool/**/uv.lock,/home/runner/work/image-composer-tool/image-composer-tool/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
pre-merge / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
pre-merge / secrets-gitleaks-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
pre-merge / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
pre-merge / trivy-critical-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/

Artifacts

Produced during runtime
Name Size Digest
gitleaks-results-dw39pb-image-composer-tool
175 Bytes
sha256:99d7c872b259da095c267d53227ce1eb9d0f7aa8ceca9afc9ffb9058b879596f
trivy-config-scan-image-composer-tool
496 Bytes
sha256:c4b9cfa35c02978803109233b419b469d6936a9a031df46e08fef7adf39cf8d4
trivy-fs-scan-report-image-composer-tool
1.29 KB
sha256:06ebd62d21cc50044b667ccb7c8d84a8527d9176fdac6f240847ca38fff581ab
zizmor-scan-report-image-composer-tool
594 Bytes
sha256:87119e5f1a6aaf531230dfc4f6d12005296d082628aaa0fc93605ffc197c5b26