Skip to content
Build and Deploy PR (Ephemeral)

Build and deploy ephemeral PR environments #27

Sign in to view logs

Build and deploy ephemeral PR environments

Build and deploy ephemeral PR environments #27

Triggered via pull request February 6, 2025 20:32
@Thomas-GeraghtyThomas-Geraghty
synchronize #62
ephemeral-prs
Status Success
Total duration 2m 18s
Artifacts 1

build_and_deploy_pr.yml

on: pull_request
Build docker image from hmpps-github-actions  /  Build Docker Image
1m 37s
Build docker image from hmpps-github-actions / Build Docker Image
Deploy to the development environment  /  Deploy to dev
22s
Deploy to the development environment / Deploy to dev
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L1
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: Dockerfile#L10
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: Dockerfile#L22
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: Dockerfile#L13
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#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/

Artifacts

Produced during runtime
Name Size
ministryofjustice~hmpps-assess-risks-and-needs-oastub-ui~1AQJ06.dockerbuild
65.5 KB