Flowzone

Unset AWS credentials to avoid overriding MinIO credentials #2289

Sign in to view logs

Triggered via pull request December 17, 2024 01:29

klutchell

opened #469

kyle/actions-cache

Status Success

Total duration 7m 33s

Artifacts 5

flowzone.yml

on: pull_request

Matrix: Flowzone / Event Types

Flowzone / Versioned source

Flowzone / actionlint

Flowzone / octoscan

Flowzone / File list

Flowzone / Clean GitHub release

Flowzone / Is custom

Flowzone / Is rust

Flowzone / Is npm

Flowzone / Is python

Flowzone / Is docker

Flowzone / Generate release notes

Flowzone / Is balena

Flowzone / Is website

Flowzone / Is CloudFormation

Flowzone / Pre-commit hooks

Matrix: Flowzone / Test custom

Matrix: Flowzone / Clean custom

Matrix: Flowzone / Finalize custom

Matrix: Flowzone / Test rust

Flowzone / Finalize rust

Matrix: Flowzone / Test npm

Flowzone / Finalize npm

Flowzone / Finalize npm docs

Matrix: Flowzone / Test python poetry

Flowzone / Finalize python

Matrix: Flowzone / Test docker

Matrix: Flowzone / Finalize docker

Flowzone / Prepare deploy message

Flowzone / Finalize GitHub release

Matrix: Flowzone / Finalize balena

Matrix: Flowzone / Test CloudFormation

Matrix: Flowzone / Finalize CloudFormation

Flowzone / Generate SBOM for cargo

Flowzone / Generate SBOM for NPM

Flowzone / Generate SBOM for python

Matrix: Flowzone / Publish custom

Matrix: Flowzone / Publish rust

Flowzone / Publish npm

Flowzone / Publish to test PyPI

Matrix: Flowzone / Publish balena

Flowzone / Publish website

Matrix: Flowzone / Publish docker

Flowzone / All tests

Matrix: Flowzone / Always custom

Flowzone / Publish Github release

Flowzone / All jobs

Flowzone / Auto-merge

Annotations

2 errors and 11 warnings

Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, yocto-build-env, yocto-build-env, amd64)

Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers

Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, balena-push-env, balena-push-env, amd64)

Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers

Flowzone / Event Types (pull_request, opened)

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: automation/Dockerfile_balena-push-env#L18

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: automation/Dockerfile_balena-push-env#L27

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: automation/Dockerfile_balena-push-env#L8

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: automation/Dockerfile_balena-push-env#L9

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: automation/Dockerfile_yocto-build-env#L14

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: automation/Dockerfile_yocto-build-env#L29

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/

Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, yocto-build-env, yocto-build-env, amd64)

gpg: key "FB5DB77FD5C118B80511ADA8A6310ACC4672475C" not found gpg: FB5DB77FD5C118B80511ADA8A6310ACC4672475C: delete key failed: Not found

Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, yocto-build-env, yocto-build-env, amd64)

Publishing Docker images without docker compose tests!

Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, balena-push-env, balena-push-env, amd64)

gpg: key "FB5DB77FD5C118B80511ADA8A6310ACC4672475C" not found gpg: FB5DB77FD5C118B80511ADA8A6310ACC4672475C: delete key failed: Not found

Flowzone / Publish docker (ghcr.io/balena-os/balena-yocto-scripts, balena-push-env, balena-push-env, amd64)

Publishing Docker images without docker compose tests!

Artifacts

Produced during runtime

Name	Size
balena-os~balena-yocto-scripts~DIW6VZ.dockerbuild	141 KB
balena-os~balena-yocto-scripts~H46UNR.dockerbuild	67.2 KB
docker-balena-push-env-amd64	277 MB
docker-yocto-build-env-amd64	481 MB
release-notes	222 Bytes