Skip to content

Update Submodules #4749

Update Submodules

Update Submodules #4749

Triggered via pull request September 28, 2024 17:48
Status Success
Total duration 19m 38s
Artifacts 3

test.yml

on: pull_request
build-test-deploy-container
19m 29s
build-test-deploy-container
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
The 'as' keyword should match the case of the 'from' keyword: workflow-container/Dockerfile#L7
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: workflow-container/Dockerfile#L35
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-test-deploy-container: .github/workflows/test.yml#L1
Java used up to 4.87603GB of RAM
The 'as' keyword should match the case of the 'from' keyword: workflow-container/Dockerfile#L7
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: workflow-container/Dockerfile#L35
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: workflow-container/Dockerfile#L75
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
pidstat.txt
41.3 KB
viperproject~gobra~8DFKN6.dockerbuild
69.3 KB
viperproject~gobra~LGAZSL.dockerbuild
49.5 KB