Skip to content
Docker Images

Test refactoring: use tmp path fixture to mock remote and local for t… #1651

Sign in to view logs

Test refactoring: use tmp path fixture to mock remote and local for t…

Test refactoring: use tmp path fixture to mock remote and local for t… #1651

Triggered via push November 29, 2024 14:03
@unkcpzunkcpz
pushed 197c666
main
Status Success
Total duration 21m 4s
Artifacts 2

docker.yml

on: push
build-amd64  /  linux/amd64
1m 55s
build-amd64 / linux/amd64
Matrix: test-amd64
build  /  linux/amd64,linux/arm64
11m 53s
build / linux/amd64,linux/arm64
test-arm64  /  test
3m 28s
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~60KTBD+2.dockerbuild
315 KB
aiidateam~aiida-core~EWKSS9+2.dockerbuild
720 KB