Skip to content
Build and Push to Greenbone Registry

Refactor: pylint requires more complexity 80 lw. #75

Sign in to view logs

Refactor: pylint requires more complexity 80 lw.

Refactor: pylint requires more complexity 80 lw. #75

Triggered via push December 10, 2024 13:33
@nichtsfreinichtsfrei
pushed a14dfdc
main
Status Success
Total duration 14m 40s
Artifacts 1

push.yml

on: push
Build and Push to Greenbone Registry  /  build-amd64
4m 15s
Build and Push to Greenbone Registry / build-amd64
Build and Push to Greenbone Registry  /  build-arm64
7m 37s
Build and Push to Greenbone Registry / build-arm64
Build and Push to Greenbone Registry  /  create-multi-arch-manifest
23s
Build and Push to Greenbone Registry / create-multi-arch-manifest
Build and Push to Greenbone Registry  /  harbor-replication
7s
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/prod.Dockerfile#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/
Legacy key/value format with whitespace separator should not be used: .docker/prod.Dockerfile#L30
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/prod.Dockerfile#L31
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/prod.Dockerfile#L8
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/prod.Dockerfile#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/
Legacy key/value format with whitespace separator should not be used: .docker/prod.Dockerfile#L30
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/prod.Dockerfile#L31
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/prod.Dockerfile#L8
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Build and Push to Greenbone Registry / build-arm64
Process "docker run" closed with code 1

Artifacts

Produced during runtime
Name Size
greenbone~ospd-openvas~4IE0UH.dockerbuild Expired
71.8 KB