Skip to content
Docker Images

CI: Utilize uv lockfile for reproducible test environments (#6640) #1658

Sign in to view logs

CI: Utilize uv lockfile for reproducible test environments (#6640)

CI: Utilize uv lockfile for reproducible test environments (#6640) #1658

Triggered via push December 5, 2024 17:17
@unkcpzunkcpz
pushed 04cc344
main
Status Success
Total duration 21m 47s
Artifacts 2

docker.yml

on: push
build-amd64  /  linux/amd64
2m 50s
build-amd64 / linux/amd64
Matrix: test-amd64
build  /  linux/amd64,linux/arm64
11m 40s
build / linux/amd64,linux/arm64
test-arm64  /  test
3m 31s
test-arm64 / test
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~KG93GZ+2.dockerbuild
455 KB
aiidateam~aiida-core~N21ZWN+2.dockerbuild
905 KB