Skip to content
CI

Bumped AlmaLinux python to 3.12 to support ansible-core 2.20 #856

Sign in to view logs

Bumped AlmaLinux python to 3.12 to support ansible-core 2.20

Bumped AlmaLinux python to 3.12 to support ansible-core 2.20 #856

Triggered via pull request December 6, 2025 13:56
@haxorofhaxorof
opened #294
almalinux-py3.12-ansible2.20
Status Success
Total duration 1m 17s
Artifacts 9

ci.yml

on: pull_request
Matrix: build_push
dependabot
0s
dependabot
update_docker_hub_description
0s
update_docker_hub_description
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile.alpine#L11
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: Dockerfile.alpine#L10
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: Dockerfile.alpine#L11
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: Dockerfile.alpine#L10
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: Dockerfile.alpine#L11
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: Dockerfile.alpine#L10
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: Dockerfile.almalinux#L11
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: Dockerfile.almalinux#L10
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: Dockerfile.almalinux#L11
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: Dockerfile.almalinux#L10
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: Dockerfile.almalinux#L11
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: Dockerfile.almalinux#L10
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 Digest
haxorof~docker-ansible-core~4V64W3.dockerbuild
40 KB
sha256:15dd6881b0d920d67b6bc2a538ef7cda7155c80f93046cbdff50e7a58569ec05
haxorof~docker-ansible-core~64D7FB.dockerbuild
120 KB
sha256:16b29a85cbedfa99baa4b97d77ab3319471d5aef56196a66dacf46c26c953fc8
haxorof~docker-ansible-core~F11S7S.dockerbuild
117 KB
sha256:2419082c670dea630f6c14a13174630df963d3267c551531893231e375bebb66
haxorof~docker-ansible-core~M0G6QP.dockerbuild
103 KB
sha256:9cb9357f9e3fd8a7972bc2eff60726da15ac383d3d83b3f0c78b41d6ab42baec
haxorof~docker-ansible-core~MJMUJ3.dockerbuild
40.4 KB
sha256:10792603ea77d3f51daf7ba3a5ea2b6c7cbb59b6da911b84c02e5632ff68b2e1
haxorof~docker-ansible-core~SV6OTP.dockerbuild
102 KB
sha256:f387a7a639c8cee06070661fc871da5a236668ef8abb36f0b79a8f5928ee0240
haxorof~docker-ansible-core~T6G9HR.dockerbuild
40.6 KB
sha256:81da873ad5a3772d93d0bdf02f0ca822e3ca90679e9671ae65fc6a70c05dd5d8
haxorof~docker-ansible-core~V64GEY.dockerbuild
103 KB
sha256:439802e344a521b315721a97259be6fcbdf73e0b8f08b63bdb549724816d757f
haxorof~docker-ansible-core~Z2CFKM.dockerbuild
120 KB
sha256:e8cf202363c5215824108f5bf6eacb01a6d29a860b072b57ec71c7fd45d40a59