Deploy to staging #10
wangyuan0916staging-build.yaml
on: push
Get metadata to build
2s
Staging build matrix
12s
staging-build-images
/
Extract any supporting metadata
6s
staging-build-macos-packages
/
Extract any supporting metadata
7s
staging-build-windows-packages
/
Determine build info
6s
Matrix: staging-build-packages / call-build-linux-packages
staging-build-packages
/
Extract any supporting metadata
15s
Matrix: staging-build-images / Windows container images
staging-build-images
/
Multiarch container images to GHCR
2h 25m
Matrix: staging-build-macos-packages / call-build-macos-package
Matrix: staging-build-windows-packages / call-build-windows-package
staging-build-packages
/
Create repo metadata in S3
0s
staging-build-images
/
call-build-images-generate-schema
7s
staging-build-images
/
Trivy + Dockle image scan
2m 28s
staging-build-images
/
Deploy and sign multi-arch container image manifests
4s
Matrix: staging-build-macos-packages / Handle upload to S3
staging-build-windows-packages
/
Handle upload to S3
7s
staging-build-upload-schema-s3
0s
Annotations
32 errors and 28 warnings
|
staging-build-packages / amazonlinux/2.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / Extract any supporting metadata
Process completed with exit code 1.
|
|
staging-build-packages / centos/7 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / amazonlinux/2 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / amazonlinux/2023 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / centos/8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / debian/bullseye package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / ubuntu/18.04 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / ubuntu/22.04 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / debian/buster package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / ubuntu/20.04 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / ubuntu/16.04 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / debian/bookworm package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / centos/9 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-macos-packages / Handle upload to S3 (Normal macOS-latest package (Intel), macos-12)
Process completed with exit code 1.
|
|
staging-build-macos-packages / Handle upload to S3 (Apple Silicon macOS package, macos-14)
Process completed with exit code 1.
|
|
staging-build-packages / ubuntu/24.04 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-windows-packages / Handle upload to S3
Process completed with exit code 127.
|
|
staging-build-packages / centos/7.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / raspbian/buster package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / raspbian/bullseye package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / ubuntu/18.04.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / debian/buster.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / debian/bullseye.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / centos/8.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / ubuntu/20.04.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / ubuntu/22.04.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / centos/9.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / debian/bookworm.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-packages / ubuntu/24.04.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
staging-build-images / Deploy and sign multi-arch container image manifests
Process completed with exit code 1.
|
|
staging-build-packages / amazonlinux/2023.arm64v8 package build and stage to S3
Process completed with exit code 1.
|
|
Staging 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/
|
|
staging-build-macos-packages / 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
|
|
staging-build-macos-packages / call-build-macos-package (Apple Silicon macOS runner, macos-14)
openssl@3 3.3.2 is already installed and up-to-date.
To reinstall 3.3.2, run:
brew reinstall openssl@3
|
|
staging-build-macos-packages / 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
|
|
staging-build-macos-packages / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
|
|
staging-build-macos-packages / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
bison 3.8.2 is already installed and up-to-date.
To reinstall 3.8.2, run:
brew reinstall bison
|
|
staging-build-macos-packages / 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
|
|
staging-build-macos-packages / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
openssl@3 3.3.2 is already installed and up-to-date.
To reinstall 3.3.2, run:
brew reinstall openssl@3
|
|
staging-build-macos-packages / 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
|
|
staging-build-macos-packages / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|
|
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#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#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#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#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#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/
|
|
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/
|
|
staging-build-images / Trivy + Dockle image scan
The following actions use a deprecated Node.js version and will be forced to run on node20: jaxxstorm/action-install-gh-release@v1.10.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
fluent-bit-schema-3.1.9
|
67.1 KB |
|
|
macos-packages on macos-12
|
7.91 MB |
|
|
macos-packages on macos-14
|
8 MB |
|
|
packages-3.1.9-amazonlinux-2
|
16.7 MB |
|
|
packages-3.1.9-amazonlinux-2023
|
6.43 MB |
|
|
packages-3.1.9-amazonlinux-2023.arm64v8
|
6.28 MB |
|
|
packages-3.1.9-centos-7
|
15.4 MB |
|
|
packages-3.1.9-centos-7.arm64v8
|
14.7 MB |
|
|
packages-3.1.9-centos-8
|
6.81 MB |
|
|
packages-3.1.9-centos-8.arm64v8
|
6.31 MB |
|
|
packages-3.1.9-centos-9
|
6.45 MB |
|
|
packages-3.1.9-centos-9.arm64v8
|
6.29 MB |
|
|
packages-3.1.9-debian-bookworm
|
40.2 MB |
|
|
packages-3.1.9-debian-bookworm.arm64v8
|
39.6 MB |
|
|
packages-3.1.9-debian-bullseye
|
40.1 MB |
|
|
packages-3.1.9-debian-bullseye.arm64v8
|
39.7 MB |
|
|
packages-3.1.9-debian-buster
|
43.2 MB |
|
|
packages-3.1.9-debian-buster.arm64v8
|
42.8 MB |
|
|
packages-3.1.9-raspbian-bullseye
|
38.3 MB |
|
|
packages-3.1.9-raspbian-buster
|
41.4 MB |
|
|
packages-3.1.9-ubuntu-16.04
|
35.7 MB |
|
|
packages-3.1.9-ubuntu-18.04
|
43.4 MB |
|
|
packages-3.1.9-ubuntu-18.04.arm64v8
|
43.2 MB |
|
|
packages-3.1.9-ubuntu-20.04
|
43.8 MB |
|
|
packages-3.1.9-ubuntu-20.04.arm64v8
|
43.4 MB |
|
|
packages-3.1.9-ubuntu-22.04
|
39.9 MB |
|
|
packages-3.1.9-ubuntu-22.04.arm64v8
|
39.4 MB |
|
|
packages-3.1.9-ubuntu-24.04
|
39.9 MB |
|
|
packages-3.1.9-ubuntu-24.04.arm64v8
|
39.4 MB |
|
|
pivotal~fluent-bit~RBZYO6.dockerbuild
|
5.16 MB |
|
|
pivotal~fluent-bit~WGG8AC.dockerbuild
|
288 KB |
|
|
source-3.1.9
|
25.8 MB |
|
|
windows-packages-amd64_arm64
|
71.5 MB |
|
|
windows-packages-x64
|
77 MB |
|
|
windows-packages-x86
|
70.6 MB |
|