Skip to content

Using https instead of git, to pull the gem #4

Using https instead of git, to pull the gem

Using https instead of git, to pull the gem #4

Triggered via push February 10, 2026 15:18
Status Success
Total duration 3m 50s
Artifacts 1

build_image.yaml

on: push
build-fb-runner
3m 42s
build-fb-runner
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L58
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L50
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#L49
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#L42
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 Digest
cabinetoffice~fb-runner~I8HN90.dockerbuild Expired
46.6 KB
sha256:0ac96f8e5634666a703c66a7d3f28700e1255f54d513ef95c61dee17c454ed91