Deployment With integration of workflows #7
Triggered via pull request
December 3, 2024 23:00
niclasheun
Status
Failure
Total duration
30d 0h 11m 20s
Artifacts
4
dev.yml
on: pull_request
build-and-push-clients
/
...
/
Build Docker Image for ghcr.io/ls1intum/prompt2/prompt-clients-base
2m 9s
build-and-push-server
/
...
/
Build Docker Image for ghcr.io/ls1intum/prompt2/prompt-server-core
5m 12s
build-and-push-clients
/
...
/
Build Docker Image for ghcr.io/ls1intum/prompt2/prompt-clients-core
8m 53s
build-and-push-clients
/
...
/
Build Docker Image for ghcr.io/ls1intum/prompt2/prompt-clients-template-component
5m 8s
deploy-dev-container
/
deploy
0s
Annotations
1 error and 11 warnings
|
deploy-dev-container / deploy
The deployment was rejected or didn't satisfy other protection rules.
|
|
build-and-push-clients / build-and-push-clients-base / Build Docker Image for ghcr.io/ls1intum/prompt2/prompt-clients-base
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
The 'as' keyword should match the case of the 'from' keyword:
clients/Dockerfile#L3
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:
clients/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-and-push-server / build-and-push-server-core / Build Docker Image for ghcr.io/ls1intum/prompt2/prompt-server-core
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-and-push-clients / build-and-push-clients-template / Build Docker Image for ghcr.io/ls1intum/prompt2/prompt-clients-template-component
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
The 'as' keyword should match the case of the 'from' keyword:
clients/template_component/Dockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
build-and-push-clients / build-and-push-clients-core / Build Docker Image for ghcr.io/ls1intum/prompt2/prompt-clients-core
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:
clients/core/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:
clients/core/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/
|
|
Legacy key/value format with whitespace separator should not be used:
clients/core/Dockerfile#L11
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:
clients/core/Dockerfile#L12
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 | |
|---|---|---|
|
ls1intum~prompt2~JIE71A.dockerbuild
|
91.2 KB |
|
|
ls1intum~prompt2~K708SK.dockerbuild
|
70.9 KB |
|
|
ls1intum~prompt2~OR9MFY.dockerbuild
|
91.4 KB |
|
|
ls1intum~prompt2~VNH75A.dockerbuild
|
70.8 KB |
|