Skip to content
test

Updates submodules #4758

Sign in to view logs

Updates submodules

Updates submodules #4758

Triggered via push November 1, 2024 06:00
@viper-adminviper-admin
pushed bd94b72
auto-update-submodules
Status Success
Total duration 21m 45s
Artifacts 3

test.yml

on: push
build-test-deploy-container
21m 37s
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.75997GB 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.1 KB
viperproject~gobra~FKVF2F.dockerbuild
47.2 KB
viperproject~gobra~OF65BC.dockerbuild
98.6 KB