Fixes Issue #781 by converting paths first to absolut paths before re… #4725
test.yml
on: push
build-test-deploy-container
16m 4s
Annotations
7 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.95568GB of RAM
|
build-test-deploy-container:
.github/workflows/test.yml#L1
Z3 used up to 0.619868GB 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.8 KB |
|
viperproject~gobra~9IX7FO.dockerbuild
|
50.5 KB |
|
viperproject~gobra~TY2KPV.dockerbuild
|
36.4 KB |
|