Skip to content
CI

Add ordering selector for project object list #2485

Sign in to view logs

Add ordering selector for project object list

Add ordering selector for project object list #2485

Triggered via pull request November 20, 2024 07:54
@mmoilammoila
opened #1405
feature/project-object-list-ordering
Status Success
Total duration 5m 5s
Artifacts 1

ci.yaml

on: pull_request
Test frontend
53s
Test frontend
Test backend
27s
Test backend
Test shared
14s
Test shared
Test E2E
4m 55s
Test E2E
Build
2m 15s
Build
Push
0s
Push
Deploy
0s
Deploy
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L43
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#L46
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#L80
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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L82
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L10
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
Tampere~Hanna~S5UZUL.dockerbuild
59.9 KB