Skip to content
Build and Push to Greenbone Registry

Deps: Bump the github-actions group with 3 updates #141

Sign in to view logs

Deps: Bump the github-actions group with 3 updates

Deps: Bump the github-actions group with 3 updates #141

Triggered via push January 13, 2025 11:29
@greenbonebotgreenbonebot
pushed ce81de1
main
Status Success
Total duration 4m 3s
Artifacts 2

push.yml

on: push
Build and Push to Greenbone Registry  /  build-amd64
1m 51s
Build and Push to Greenbone Registry / build-amd64
Build and Push to Greenbone Registry  /  build-arm64
2m 57s
Build and Push to Greenbone Registry / build-arm64
Build and Push to Greenbone Registry  /  create-multi-arch-manifest
22s
Build and Push to Greenbone Registry / create-multi-arch-manifest
Build and Push to Greenbone Registry  /  harbor-replication
6s
Build and Push to Greenbone Registry / harbor-replication
Build and Push to Greenbone Registry  /  ...  /  notify-mattermost
10s
Build and Push to Greenbone Registry / notify / notify-mattermost
Build and Push to Greenbone Registry  /  building-product-compose
0s
Build and Push to Greenbone Registry / building-product-compose
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
Legacy key/value format with whitespace separator should not be used: .docker/Dockerfile#L22
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: .docker/Dockerfile#L23
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: .docker/Dockerfile#L24
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: .docker/Dockerfile#L1
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: .docker/Dockerfile#L23
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: .docker/Dockerfile#L24
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: .docker/Dockerfile#L1
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: .docker/Dockerfile#L22
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 and Push to Greenbone Registry / notify / notify-mattermost
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@6849a6489940f00c2f30c0fb92c6274307ccb58a. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Artifacts

Produced during runtime
Name Size
greenbone~gvm-tools~N0VP71.dockerbuild
39.1 KB
greenbone~gvm-tools~P15YB1.dockerbuild
39.2 KB