Skip to content

Bump ansible-core from 2.16.13 to 2.17.7 in /requirements/v2.16 #696

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

Bump ansible-core from 2.16.13 to 2.17.7 in /requirements/v2.16 #696

Triggered via pull request December 4, 2024 19:24
Status Success
Total duration 2m 14s
Artifacts 9

ci.yml

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

Annotations

22 warnings
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 (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.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 (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#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.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 (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 (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.16)
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
dependabot
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~8AXE0A.dockerbuild
37.3 KB
haxorof~docker-ansible-core~KY27DP.dockerbuild
37 KB
haxorof~docker-ansible-core~L80UEZ.dockerbuild
31.2 KB
haxorof~docker-ansible-core~MGYKTS.dockerbuild
30.5 KB
haxorof~docker-ansible-core~OTJX9M.dockerbuild
120 KB
haxorof~docker-ansible-core~QTEI29.dockerbuild
29.9 KB
haxorof~docker-ansible-core~W6SB2G.dockerbuild
120 KB
haxorof~docker-ansible-core~YK30S4.dockerbuild
36 KB
haxorof~docker-ansible-core~ZMK2AX.dockerbuild
117 KB