Skip to content
Deploy

Accept project ids in permission endpoints #2180

Sign in to view logs

Accept project ids in permission endpoints

Accept project ids in permission endpoints #2180

Triggered via push January 10, 2025 10:28
@MiniDiggerMiniDigger
pushed e7c2ad9
staging
Status Success
Total duration 5m 1s
Artifacts 2

deploy.yml

on: push
build
4m 30s
build
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: chart/dockerfiles/frontend/Dockerfile#L5
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: chart/dockerfiles/frontend/Dockerfile#L6
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/
Relative workdir without an absolute workdir declared within the build can have unexpected results if the base image changes: chart/dockerfiles/backend/Dockerfile#L7
WorkdirRelativePath: Relative workdir "hangar" can have unexpected results if the base image changes More info: https://docs.docker.com/go/dockerfile/rule/workdir-relative-path/
Legacy key/value format with whitespace separator should not be used: chart/dockerfiles/backend/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/

Artifacts

Produced during runtime
Name Size
HangarMC~Hangar~7F1JPS.dockerbuild
43.1 KB
HangarMC~Hangar~SHHY9T.dockerbuild
39.8 KB