Skip to content

Updates submodules (#780) #4729

Updates submodules (#780)

Updates submodules (#780) #4729

Triggered via push September 4, 2024 15:46
Status Success
Total duration 15m 50s
Artifacts 3

test.yml

on: push
build-test-deploy-container
15m 39s
build-test-deploy-container
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
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/
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/
build-test-deploy-container: .github/workflows/test.yml#L1
Java used up to 4.79722GB 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
45.3 KB
viperproject~gobra~0L90PU.dockerbuild
35.7 KB
viperproject~gobra~F7Z1SM.dockerbuild
41.6 KB