Skip to content

github-action: bump docker/build-push-action from 5.0.0 to 6.13.0 #263

github-action: bump docker/build-push-action from 5.0.0 to 6.13.0

github-action: bump docker/build-push-action from 5.0.0 to 6.13.0 #263

Triggered via pull request February 3, 2025 23:16
Status Failure
Total duration 3m 26s
Artifacts 1
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
workflows / deploy
The current runner (ubuntu-24.04-x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported). In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml $ ruby-build 3.1.0 /opt/hostedtoolcache/Ruby/3.1.0/x64 Once that completes successfully, mark it as complete with: $ touch /opt/hostedtoolcache/Ruby/3.1.0/x64.complete It is your responsibility to ensure installing Ruby like that is not done in parallel.
Legacy key/value format with whitespace separator should not be used: cf-acceptance-tests/Dockerfile#L24
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: cf-acceptance-tests/Dockerfile#L40
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: cf-acceptance-tests/Dockerfile#L19
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: cf-acceptance-tests/Dockerfile#L20
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: cf-acceptance-tests/Dockerfile#L22
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: cf-acceptance-tests/Dockerfile#L23
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
alphagov~paas-docker-cloudfoundry-tools~IJIZ2E.dockerbuild
293 KB