Unstable build #2162
edsipercron-unstable-build.yaml
on: schedule
Get metadata to add to build
3s
unstable-build-images
/
Extract any supporting metadata
9s
unstable-build-macos-package
/
Extract any supporting metadata
7s
unstable-build-windows-package
/
Determine build info
8s
Matrix: unstable-build-images / Windows container images
unstable-build-images
/
Multiarch container images to GHCR
2h 20m
Matrix: unstable-build-packages / call-build-linux-packages
unstable-build-packages
/
Extract any supporting metadata
9s
Matrix: unstable-build-macos-package / call-build-macos-package
Matrix: unstable-build-windows-package / call-build-windows-package
unstable-build-images
/
call-build-images-generate-schema
7s
unstable-build-images
/
Trivy + Dockle image scan
15s
unstable-build-images
/
Deploy and sign multi-arch container image manifests
5s
unstable-build-packages
/
Create repo metadata in S3
0s
Matrix: unstable-build-macos-package / Handle upload to S3
unstable-build-windows-package
/
Handle upload to S3
0s
unstable-release
0s
Annotations
11 errors and 39 warnings
|
unstable-build-packages / centos/7.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
unstable-build-packages / centos/7 package build and stage to S3
Process completed with exit code 1.
|
|
unstable-build-packages / amazonlinux/2 package build and stage to S3
The action 'Retrieve target info for repo creation' has timed out after 5 minutes.
|
|
unstable-build-packages / ubuntu/16.04 package build and stage to S3
The action 'Retrieve target info for repo creation' has timed out after 5 minutes.
|
|
unstable-build-packages / amazonlinux/2023 package build and stage to S3
The action 'Retrieve target info for repo creation' has timed out after 5 minutes.
|
|
unstable-build-packages / debian/bookworm package build and stage to S3
The action 'Retrieve target info for repo creation' has timed out after 5 minutes.
|
|
unstable-build-packages / ubuntu/20.04 package build and stage to S3
The action 'Retrieve target info for repo creation' has timed out after 5 minutes.
|
|
unstable-build-windows-package / call-build-windows-package (Windows 64bit, x64, C:\vcpkg\packages\openssl_x64-windows-static, x64...
Process completed with exit code 1.
|
|
unstable-build-windows-package / call-build-windows-package (Windows 64bit (Arm64), amd64_arm64, C:\vcpkg\packages\openssl_arm64-w...
Process completed with exit code 1.
|
|
unstable-build-windows-package / call-build-windows-package (Windows 32bit, x86, C:\vcpkg\packages\openssl_x86-windows-static, x86...
Process completed with exit code 1.
|
|
unstable-build-images / Deploy and sign multi-arch container image manifests
Process completed with exit code 1.
|
|
unstable build matrix
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
unstable-build-packages / centos/7.arm64v8 package build and stage to S3
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.317.0. Please update to the latest version 2.319.1
|
|
unstable-build-macos-package / call-build-macos-package (Apple Silicon macOS runner, macos-14)
libyaml 0.2.5 is already installed and up-to-date.
To reinstall 0.2.5, run:
brew reinstall libyaml
|
|
unstable-build-macos-package / call-build-macos-package (Apple Silicon macOS runner, macos-14)
pkg-config 0.29.2_3 is already installed and up-to-date.
To reinstall 0.29.2_3, run:
brew reinstall pkg-config
|
|
unstable-build-macos-package / call-build-macos-package (Apple Silicon macOS runner, macos-14)
These files were overwritten during the `brew link` step:
|
|
unstable-build-packages / amazonlinux/2.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
libyaml 0.2.5 is already installed and up-to-date.
To reinstall 0.2.5, run:
brew reinstall libyaml
|
|
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
pkg-config 0.29.2_3 is already installed and up-to-date.
To reinstall 0.29.2_3, run:
brew reinstall pkg-config
|
|
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
These files were overwritten during the `brew link` step:
|
|
unstable-build-packages / centos/8.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-packages / amazonlinux/2023.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-packages / debian/buster.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-packages / centos/9.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-packages / debian/bullseye.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-packages / ubuntu/18.04.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-packages / ubuntu/22.04.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-packages / debian/bookworm.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-packages / ubuntu/20.04.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
unstable-build-packages / ubuntu/24.04.arm64v8 package build and stage to S3
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
|
|
|
|
|
|
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L188
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
dockerfiles/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L17
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L20
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L64
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L100
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L157
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L17
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L20
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L64
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L157
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L188
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
dockerfiles/Dockerfile#L100
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
dockerfiles/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
dockerfiles/Dockerfile#L206
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
fluent-bit-schema-3.0
|
65.8 KB |
|
|
fluent~fluent-bit~JORCCM.dockerbuild
|
285 KB |
|
|
fluent~fluent-bit~K2MMA1.dockerbuild
|
5.25 MB |
|
|
macos-packages on macos-12
|
7.78 MB |
|
|
macos-packages on macos-14
|
7.86 MB |
|
|
packages-3.0-amazonlinux-2
|
16.1 MB |
|
|
packages-3.0-amazonlinux-2.arm64v8
|
15.9 MB |
|
|
packages-3.0-amazonlinux-2023
|
6.31 MB |
|
|
packages-3.0-amazonlinux-2023.arm64v8
|
6.13 MB |
|
|
packages-3.0-centos-8
|
6.7 MB |
|
|
packages-3.0-centos-8.arm64v8
|
6.17 MB |
|
|
packages-3.0-centos-9
|
6.33 MB |
|
|
packages-3.0-centos-9.arm64v8
|
6.14 MB |
|
|
packages-3.0-debian-bookworm
|
38.3 MB |
|
|
packages-3.0-debian-bookworm.arm64v8
|
37.8 MB |
|
|
packages-3.0-debian-bullseye
|
38.6 MB |
|
|
packages-3.0-debian-bullseye.arm64v8
|
38 MB |
|
|
packages-3.0-debian-buster
|
41.5 MB |
|
|
packages-3.0-debian-buster.arm64v8
|
41.2 MB |
|
|
packages-3.0-raspbian-bullseye
|
36.6 MB |
|
|
packages-3.0-raspbian-buster
|
39.7 MB |
|
|
packages-3.0-ubuntu-16.04
|
35.3 MB |
|
|
packages-3.0-ubuntu-18.04
|
43.1 MB |
|
|
packages-3.0-ubuntu-18.04.arm64v8
|
42.8 MB |
|
|
packages-3.0-ubuntu-20.04
|
43.4 MB |
|
|
packages-3.0-ubuntu-20.04.arm64v8
|
43 MB |
|
|
packages-3.0-ubuntu-22.04
|
39.5 MB |
|
|
packages-3.0-ubuntu-22.04.arm64v8
|
39 MB |
|
|
packages-3.0-ubuntu-24.04
|
39.4 MB |
|
|
packages-3.0-ubuntu-24.04.arm64v8
|
38.9 MB |
|
|
source-3.0
|
26 MB |
|