Skip to content

Bump org.assertj:assertj-core from 3.27.1 to 3.27.3 #637

Bump org.assertj:assertj-core from 3.27.1 to 3.27.3

Bump org.assertj:assertj-core from 3.27.1 to 3.27.3 #637

Triggered via push February 2, 2025 03:02
Status Success
Total duration 10m 39s
Artifacts 3

ci-main.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L11
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "S3PROXY_ENCRYPTED_BLOBSTORE_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L11
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "JCLOUDS_CREDENTIAL") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L11
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "S3PROXY_CREDENTIAL") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L11
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "S3PROXY_KEYSTORE_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L11
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "S3PROXY_CORS_ALLOW_CREDENTIAL") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size
gaul~s3proxy~YFHMAB.dockerbuild
145 KB
pom
3.34 KB
s3proxy
36.2 MB