Skip to content

implement has_key filter for SQLite backend #1637

implement has_key filter for SQLite backend

implement has_key filter for SQLite backend #1637

Triggered via push November 19, 2024 10:08
Status Success
Total duration 22m 38s
Artifacts 2

docker.yml

on: push
build-amd64  /  linux/amd64
2m 22s
build-amd64 / linux/amd64
Matrix: test-amd64
build  /  linux/amd64,linux/arm64
12m 33s
build / linux/amd64,linux/arm64
Matrix: publish-ghcr / release
Matrix: publish-dockerhub / release
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Legacy key/value format with whitespace separator should not be used: .docker/aiida-core-base/Dockerfile#L27
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: .docker/aiida-core-base/Dockerfile#L148
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: .docker/aiida-core-base/Dockerfile#L27
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: .docker/aiida-core-base/Dockerfile#L148
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
aiidateam~aiida-core~EN1NOQ+2.dockerbuild
450 KB
aiidateam~aiida-core~GVT263+2.dockerbuild
783 KB