Container release pipeline #116
RouHimpipeline.yml
on: schedule
Check container file
10s
build-test-push-image
3m 1s
Annotations
6 warnings
|
Check container file
The following actions use a deprecated Node.js version and will be forced to run on node20: jaxxstorm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-test-push-image
The following actions use a deprecated Node.js version and will be forced to run on node20: jaxxstorm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Legacy key/value format with whitespace separator should not be used:
container-data/Containerfile#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/
|
|
Legacy key/value format with whitespace separator should not be used:
container-data/Containerfile#L5
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:
container-data/Containerfile#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/
|
|
Legacy key/value format with whitespace separator should not be used:
container-data/Containerfile#L5
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 | |
|---|---|---|
|
RouHim~sons-of-the-forest-container-image~JR43T0.dockerbuild
|
26.5 KB |
|
|
RouHim~sons-of-the-forest-container-image~V4RH2J.dockerbuild
|
26.3 KB |
|