fix(deps): update jackson #2314
renovate[bot]docker-build-test.yml
on: pull_request
build-jdk
/
build-and-test
59s
Matrix: build-test
Annotations
4 errors and 12 warnings
|
build-test (docker-compose.yml, Dockerfile.graalvm-jvm.ci)
Process completed with exit code 1.
|
|
build-test (testing/docker-compose.hsqldb.yml, Dockerfile.graalvm-jvm.ci)
Process completed with exit code 1.
|
|
build-test (testing/docker-compose.cockroachdb.yml, Dockerfile.graalvm-jvm.ci)
Process completed with exit code 1.
|
|
build-test (testing/docker-compose.yugabytedb.yml, Dockerfile.graalvm-jvm.ci)
Process completed with exit code 1.
|
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile.graalvm-jvm.ci#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/
|
|
The 'as' keyword should match the case of the 'from' keyword:
Dockerfile.graalvm-jvm.ci#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
Dockerfile.graalvm-jvm.ci#L36
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/
|
|
The 'as' keyword should match the case of the 'from' keyword:
Dockerfile.graalvm-jvm.ci#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
Dockerfile.graalvm-jvm.ci#L36
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.graalvm-jvm.ci#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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
Dockerfile.graalvm-jvm.ci#L36
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.graalvm-jvm.ci#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/
|
|
The 'as' keyword should match the case of the 'from' keyword:
Dockerfile.graalvm-jvm.ci#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
Dockerfile.graalvm-jvm.ci#L36
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.graalvm-jvm.ci#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/
|
|
The 'as' keyword should match the case of the 'from' keyword:
Dockerfile.graalvm-jvm.ci#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
TeamPiped~Piped-Backend~8784VK.dockerbuild
|
17.4 KB |
sha256:3ac8be5cc64a220793640a7774a343db7eb5a5862ebc795f2d2eb8c127821d73
|
|
|
TeamPiped~Piped-Backend~ESJW7D.dockerbuild
|
25.9 KB |
sha256:36d71a64d95dc2b84ae4f307d7cf5e6562f5df21dbe74e5ebb2556367b6a610d
|
|
|
TeamPiped~Piped-Backend~FBSL4X.dockerbuild
|
25.5 KB |
sha256:99973d58bb90cff07e255b9e4c81da9071205afa7ad1761319c60b4959fce495
|
|
|
TeamPiped~Piped-Backend~K5FER2.dockerbuild
|
18.8 KB |
sha256:f3b71f1f621a897d862e3fb12ed7ed5f6c124d2a30ead353ead03bd09a618c84
|
|
|
TeamPiped~Piped-Backend~MXZEU1.dockerbuild
|
19.7 KB |
sha256:21612e75764820255cd19f2ee9e8ae2af29ad124edaceb249e5f72a30c6558cd
|
|
|
TeamPiped~Piped-Backend~N9B2Q4.dockerbuild
|
18.2 KB |
sha256:ffd09d0e016fe5ec78cfaad73c19a46e5b5d172bc5e526659f213b522ba0ed47
|
|
|
TeamPiped~Piped-Backend~PHSR2L.dockerbuild
|
17.3 KB |
sha256:701168531b05c9e05dbc9be942165cbaa936aa609452d52f3da3531e76aafb5c
|
|
|
TeamPiped~Piped-Backend~RELSAI.dockerbuild
|
18.6 KB |
sha256:a967560dc9fa872e22c096675662435fdae5a0a6c4e67fde385a1875e0cb1421
|
|
|
TeamPiped~Piped-Backend~TOEMYD.dockerbuild
|
25.4 KB |
sha256:038dcf34553dbc8109acef3f24a0031d2ad2fc03649c73c237c59ca5e121eb2c
|
|
|
TeamPiped~Piped-Backend~UJ3ZYK.dockerbuild
|
18.7 KB |
sha256:cff99bdbaa8a2f0ba4602f16f1e53fdd4b98f6ec8e58fd724af496d424cc8b4c
|
|
|
TeamPiped~Piped-Backend~UT2LLG.dockerbuild
|
24.1 KB |
sha256:f0224f320c8f848068e138ffd605428f9c088d674efaf7f3867a77e3df501706
|
|
|
TeamPiped~Piped-Backend~YYMNMK.dockerbuild
|
18.3 KB |
sha256:dfddffc971d4745450b2d6833ce3650ac212de842e51dfce3de8a7ff9db52b6b
|
|
|
piped.jar
|
76.7 MB |
sha256:f872e9b11334d3ac74d4d7611154bc9be887927f335faf36b7ee0127bce7c48d
|
|