Skip to content

Merge pull request #988 from traPtitech/fix/cannot-export-log #525

Merge pull request #988 from traPtitech/fix/cannot-export-log

Merge pull request #988 from traPtitech/fix/cannot-export-log #525

Triggered via push December 24, 2024 16:11
Status Success
Total duration 4m 8s
Artifacts 8

main.yaml

on: push
Build Base Image
3m 9s
Build Base Image
Build Dashboard Image
52s
Build Dashboard Image
Matrix: Build Component Images
Fit to window
Zoom out
Zoom in

Annotations

15 warnings
Build Dashboard Image
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Base Image
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: Dockerfile#L4
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/
Build Component Images (ns-gateway)
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: Dockerfile#L4
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/
Build Component Images (ns-controller)
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: Dockerfile#L4
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/
Build Component Images (ns-ssgen)
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: Dockerfile#L4
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/
Build Component Images (ns-builder)
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: Dockerfile#L4
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/
Build Component Images (ns-gitea-integration)
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: Dockerfile#L4
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/
Build Component Images (ns-migrate)
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: Dockerfile#L4
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
traPtitech~NeoShowcase~6ZBF05.dockerbuild
75 KB
traPtitech~NeoShowcase~6ZDSN5.dockerbuild
40.3 KB
traPtitech~NeoShowcase~CY1VMY.dockerbuild
40.1 KB
traPtitech~NeoShowcase~P5678T.dockerbuild
41.4 KB
traPtitech~NeoShowcase~PX7H0B.dockerbuild
41.6 KB
traPtitech~NeoShowcase~TXKHZI.dockerbuild
79.8 KB
traPtitech~NeoShowcase~UMOAXE.dockerbuild
61.8 KB
traPtitech~NeoShowcase~YYC52R.dockerbuild
39.8 KB