Skip to content
[builder] CI for nightly build releases

[builder] CI for nightly build releases #1708

Sign in to view logs

[builder] CI for nightly build releases

[builder] CI for nightly build releases #1708

Triggered via schedule September 18, 2024 00:11
@HenryQWHenryQW
⁠ 3317abc
main
Status Success
Total duration 1m 12s
Artifacts 1

build-nightly-release.yml

on: schedule
release
1m 1s
release
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L98
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: Dockerfile#L115
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: Dockerfile#L95
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: Dockerfile#L96
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: Dockerfile#L97
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
HenryQW~Awesome-TTRSS~LZ3KZM.dockerbuild
54.2 KB