Skip to content
Flowzone

Use S3 and GitHub Actions for yocto build cache #2012

Sign in to view logs

Use S3 and GitHub Actions for yocto build cache

Use S3 and GitHub Actions for yocto build cache #2012

Triggered via pull request November 5, 2024 15:24
@klutchellklutchell
synchronize #443
kyle/dl-mirror
Status Success
Total duration 4m 53s
Artifacts 5

flowzone.yml

on: pull_request
Matrix: Flowzone / Event Types
Flowzone  /  Versioned source
33s
Flowzone / Versioned source
Flowzone  /  Clean GitHub release
0s
Flowzone / Clean GitHub release
Flowzone  /  Is custom
11s
Flowzone / Is custom
Flowzone  /  Is rust
11s
Flowzone / Is rust
Flowzone  /  Is npm
4s
Flowzone / Is npm
Flowzone  /  Is python
4s
Flowzone / Is python
Flowzone  /  Is docker
15s
Flowzone / Is docker
Flowzone  /  Generate release notes
10s
Flowzone / Generate release notes
Flowzone  /  Is balena
0s
Flowzone / Is balena
Flowzone  /  Is website
0s
Flowzone / Is website
Flowzone  /  Is CloudFormation
0s
Flowzone / Is CloudFormation
Flowzone  /  Lint workflows
10s
Flowzone / Lint workflows
Matrix: Flowzone / Test custom
Matrix: Flowzone / Clean custom
Matrix: Flowzone / Finalize custom
Matrix: Flowzone / Test rust
Flowzone  /  Finalize rust
0s
Flowzone / Finalize rust
Matrix: Flowzone / Test npm
Flowzone  /  Finalize npm
0s
Flowzone / Finalize npm
Flowzone  /  Finalize npm docs
0s
Flowzone / Finalize npm docs
Matrix: Flowzone / Test python poetry
Flowzone  /  Finalize python
0s
Flowzone / Finalize python
Matrix: Flowzone / Test docker
Matrix: Flowzone / Finalize docker
Flowzone  /  Prepare deploy message
0s
Flowzone / Prepare deploy message
Flowzone  /  Finalize GitHub release
0s
Flowzone / Finalize GitHub release
Matrix: Flowzone / Finalize balena
Matrix: Flowzone / Test CloudFormation
Matrix: Flowzone / Finalize CloudFormation
Flowzone  /  Generate SBOM for cargo
0s
Flowzone / Generate SBOM for cargo
Flowzone  /  Generate SBOM for NPM
0s
Flowzone / Generate SBOM for NPM
Flowzone  /  Generate SBOM for python
0s
Flowzone / Generate SBOM for python
Matrix: Flowzone / Publish custom
Matrix: Flowzone / Publish rust
Flowzone  /  Publish npm
0s
Flowzone / Publish npm
Flowzone  /  Publish to test PyPI
0s
Flowzone / Publish to test PyPI
Matrix: Flowzone / Publish balena
Flowzone  /  Publish website
0s
Flowzone / Publish website
Matrix: Flowzone / Publish docker
Flowzone  /  All tests
0s
Flowzone / All tests
Matrix: Flowzone / Always custom
Flowzone  /  Publish Github release
7s
Flowzone / Publish Github release
Flowzone  /  All jobs
0s
Flowzone / All jobs
Flowzone  /  Auto-merge
4s
Flowzone / Auto-merge
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, balena-push-env, balena-push-env, amd64)
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, yocto-build-env, yocto-build-env, amd64)
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
Legacy key/value format with whitespace separator should not be used: automation/Dockerfile_balena-push-env#L8
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: automation/Dockerfile_balena-push-env#L9
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: automation/Dockerfile_balena-push-env#L18
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: automation/Dockerfile_balena-push-env#L27
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: automation/Dockerfile_yocto-build-env#L14
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: automation/Dockerfile_yocto-build-env#L29
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/
Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, balena-push-env, balena-push-env, amd64)
gpg: key "FB5DB77FD5C118B80511ADA8A6310ACC4672475C" not found gpg: FB5DB77FD5C118B80511ADA8A6310ACC4672475C: delete key failed: Not found
Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, balena-push-env, balena-push-env, amd64)
Publishing Docker images without docker compose tests!
Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, yocto-build-env, yocto-build-env, amd64)
gpg: key "FB5DB77FD5C118B80511ADA8A6310ACC4672475C" not found gpg: FB5DB77FD5C118B80511ADA8A6310ACC4672475C: delete key failed: Not found
Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, yocto-build-env, yocto-build-env, amd64)
Publishing Docker images without docker compose tests!

Artifacts

Produced during runtime
Name Size
balena-os~balena-yocto-scripts~FRV6ZI.dockerbuild
31.5 KB
balena-os~balena-yocto-scripts~I0561B.dockerbuild
34.4 KB
docker-balena-push-env-amd64 Expired
277 MB
docker-yocto-build-env-amd64 Expired
479 MB
release-notes Expired
364 Bytes