Skip to content
Back to pull request #224

Update balena/open-balena-base Docker tag to v18.0.14 #517

Sign in to view logs

Update balena/open-balena-base Docker tag to v18.0.14

Update balena/open-balena-base Docker tag to v18.0.14 #517

Triggered via pull request September 17, 2024 22:52
@balena-renovatebalena-renovate[bot]
opened #224
renovate/balena-open-balena-base-18.0.x
Status Success
Total duration 18m 17s
Artifacts 5

flowzone.yml

on: pull_request
Matrix: Flowzone / Event Types
Flowzone  /  Versioned source
28s
Flowzone / Versioned source
Flowzone  /  Clean GitHub release
0s
Flowzone / Clean GitHub release
Flowzone  /  Is custom
11s
Flowzone / Is custom
Flowzone  /  Is rust
4s
Flowzone / Is rust
Flowzone  /  Is npm
4s
Flowzone / Is npm
Flowzone  /  Is python
7s
Flowzone / Is python
Flowzone  /  Is docker
12s
Flowzone / Is docker
Flowzone  /  Generate release notes
5s
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
5s
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
6s
Flowzone / Publish Github release
Flowzone  /  All jobs
0s
Flowzone / All jobs
Flowzone  /  Auto-merge
0s
Flowzone / Auto-merge
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L17
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: Dockerfile#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: Dockerfile#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: Dockerfile#L10
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: Dockerfile#L11
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: Dockerfile#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: Dockerfile#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: Dockerfile#L10
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: Dockerfile#L11
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: Dockerfile#L17
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 (balena/open-balena-s3, default, default, amd64 arm64v8)
gpg: key "FB5DB77FD5C118B80511ADA8A6310ACC4672475C" not found gpg: FB5DB77FD5C118B80511ADA8A6310ACC4672475C: delete key failed: Not found
Flowzone / Publish docker (balena/open-balena-s3, default, default, amd64 arm64v8)
Publishing Docker images without docker compose tests!

Artifacts

Produced during runtime
Name Size
balena-io~open-balena-s3~G2LMCF.dockerbuild Expired
71.7 KB
balena-io~open-balena-s3~MVCX66.dockerbuild Expired
72.1 KB
docker-default-amd64 Expired
543 MB
docker-default-arm64v8 Expired
498 MB
release-notes Expired
451 Bytes