Skip to content
Build and push Stream Perf Test Docker image

new_release #824

Sign in to view logs

new_release

new_release #824

Triggered via repository dispatch March 10, 2025 05:03
@github-actionsgithub-actions[bot]
new_release ⁠ b620a1d
Status Success
Total duration 6m 57s
Artifacts 1

build-push-stream-perf-test-docker-image.yml

on: repository_dispatch
Push Docker image to Docker Hub
6m 49s
Push Docker image to Docker Hub
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L43
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "RABBITMQ_PGP_KEY_ID") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L75
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#L76
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#L77
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
rabbitmq~rabbitmq-stream-perf-test~QNIS7C.dockerbuild
155 KB
sha256:6f4956f2fe471a3de269eee86eef36cd1b9e4e9bf3abdb27d2a83017740e818b