Skip to content

Bump aiohappyeyeballs from 2.4.4 to 2.4.6 #551

Bump aiohappyeyeballs from 2.4.4 to 2.4.6

Bump aiohappyeyeballs from 2.4.4 to 2.4.6 #551

Triggered via pull request February 10, 2025 01:06
Status Success
Total duration 31m 19s
Artifacts 5

pr.yaml

on: pull_request_target
publish_images  /  Build and push operator image
3m 33s
publish_images / Build and push operator image
publish_images  /  Build and push ansible runner image
2m 10s
publish_images / Build and push ansible runner image
publish_images  /  Mirror and tag the latest ARA image
44s
publish_images / Mirror and tag the latest ARA image
Matrix: unit_tests / Tox unit tests and linting
publish_charts  /  Publish Helm charts to GitHub pages
24s
publish_charts / Publish Helm charts to GitHub pages
functional_tests  /  Operator functional tests via tox
2m 57s
functional_tests / Operator functional tests via tox
integration_tests  /  run_azimuth_tests
24m 6s
integration_tests / run_azimuth_tests
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
publish_images / Build and push ansible runner image
Unexpected input(s) 'github-token', valid inputs are ['checkout-path', 'cache-key', 'build-args', 'context', 'file', 'labels', 'platforms', 'pull', 'push', 'tags']
publish_images / Build and push ansible runner image
Unexpected input(s) 'github-token', valid inputs are ['checkout-path', 'cache-key', 'build-args', 'context', 'file', 'labels', 'platforms', 'pull', 'push', 'tags']
Legacy key/value format with whitespace separator should not be used: Dockerfile#L35
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#L36
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#L37
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#L48
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#L52
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/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L22
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L34
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/
publish_images / Build and push operator image
Unexpected input(s) 'github-token', valid inputs are ['checkout-path', 'cache-key', 'build-args', 'context', 'file', 'labels', 'platforms', 'pull', 'push', 'tags']
publish_images / Build and push operator image
Unexpected input(s) 'github-token', valid inputs are ['checkout-path', 'cache-key', 'build-args', 'context', 'file', 'labels', 'platforms', 'pull', 'push', 'tags']

Artifacts

Produced during runtime
Name Size
azimuth-cloud~azimuth-caas-operator~9JAWLL.dockerbuild
79.5 KB
azimuth-cloud~azimuth-caas-operator~NBYFAV.dockerbuild
79 KB
code-coverage-report
162 KB
debug-bundle
30.3 KB
test-report
224 KB