Bump version #677

Sign in to view logs

Re-run triggered October 15, 2024 17:31

tmacro

bugfix/UTAPI-109/bump_version

Status Success

Total duration 3m 4s

Artifacts 3

tests.yaml

on: push

build-ci / ... / build

build-ci / vault-ci

build-ci / ... / build

build-ci / ... / build

tests-v2-with-vault

Matrix: tests-v1

Matrix: tests-v2-without-sensision

Annotations

22 warnings

lint: libV2/server/API/metrics/listMetrics.js#L26

'start' is never reassigned. Use 'const' instead

lint: tests/functional/client/testClientConnections.js#L60

Expected to return a value at the end of arrow function

lint: tests/functional/client/testClientConnections.js#L109

Expected to return a value at the end of arrow function

lint: tests/utils/vaultclient.js#L132

Expected to return a value at the end of arrow function

The 'as' keyword should match the case of the 'from' keyword: images/warp10/Dockerfile#L1

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: images/warp10/Dockerfile#L22

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: images/warp10/Dockerfile#L30

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: images/warp10/Dockerfile#L33

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: images/warp10/Dockerfile#L57

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: images/warp10/Dockerfile#L3

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: images/redis/Dockerfile#L3

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: images/warp10/Dockerfile#L23

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: images/redis/Dockerfile#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: images/warp10/Dockerfile#L25

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: images/redis/Dockerfile#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: images/warp10/Dockerfile#L31

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: images/redis/Dockerfile#L17

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: images/warp10/Dockerfile#L34

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: .github/docker/redis-replica/Dockerfile#L12

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT 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: .github/docker/redis-replica/Dockerfile#L7

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: .github/docker/redis-replica/Dockerfile#L8

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: .github/docker/redis-replica/Dockerfile#L9

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/