Skip to content

Bump ansible-core from 2.16.13 to 2.16.14 in /requirements/v2.16 #695

Bump ansible-core from 2.16.13 to 2.16.14 in /requirements/v2.16

Bump ansible-core from 2.16.13 to 2.16.14 in /requirements/v2.16 #695

Triggered via push December 4, 2024 19:23
Status Success
Total duration 3m 26s
Artifacts 9

ci.yml

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

Annotations

22 warnings
build_push (almalinux, v2.17)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/
build_push (almalinux, v2.15)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/
build_push (alpine, v2.16)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/
build_push (almalinux, v2.16)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/
build_push (alpine, v2.15)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/
build_push (alpine, v2.17)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/
build_push (ubuntu, v2.15)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build_push (ubuntu, v2.17)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build_push (ubuntu, v2.16)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
update_docker_hub_description
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size
haxorof~docker-ansible-core~7CPSQL.dockerbuild
63.9 KB
haxorof~docker-ansible-core~873VHO.dockerbuild
47.7 KB
haxorof~docker-ansible-core~B3TKRP.dockerbuild
50.8 KB
haxorof~docker-ansible-core~GTX9J7.dockerbuild
48.1 KB
haxorof~docker-ansible-core~HIZID9.dockerbuild
140 KB
haxorof~docker-ansible-core~ULDFNP.dockerbuild
52.2 KB
haxorof~docker-ansible-core~VVS7T1.dockerbuild
135 KB
haxorof~docker-ansible-core~Y00OJZ.dockerbuild
130 KB
haxorof~docker-ansible-core~ZPTLFD.dockerbuild
54 KB