Fix: error output on scannerctl syntax check #1900
control.yml
on: pull_request
functional
/
build-image
17m 17s
functional
/
build-rs
17m 18s
adapt_release
5s
unit-tests
/
C
5m 53s
unit-tests
/
Rust
6m 49s
linting
/
C
6s
linting
/
Rust
2m 51s
linting
/
Rust-Typos
22s
linting
/
Rust-Audit
2m 46s
linting
/
License-Headers
4s
Matrix: functional / distributed-monolith-railguard
functional
/
smoketest
8m 59s
functional
/
tests
11m 55s
container
/
...
/
build-amd64
2m 45s
container
/
...
/
build-arm64
0s
container
/
ghcr:debian:stable:arm64
20m 28s
container
/
ghcr:debian:stable
14m 33s
container
/
ghcr:debian:testing
13m 49s
container
/
ghcr:debian:oldstable
2m 28s
container
/
...
/
create-multi-arch-manifest
0s
container
/
...
/
notify-mattermost
container
/
...
/
harbor-replication
0s
container
/
...
/
building-product-compose
0s
Annotations
2 errors and 6 warnings
container / greenbone-reg:debian:stable / build-amd64
buildx failed with: ERROR: failed to solve: registry.community.greenbone.net/community/gvm-libs:edge: failed to resolve source metadata for registry.community.greenbone.net/community/gvm-libs:edge: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry.community.greenbone.net/v2/community/gvm-libs/manifests/sha256:ef78600b55cfd49015a0edc5dec5991a1d351cd48384c84ad3995e1e8d363f5f: 502 Bad Gateway
|
container / ghcr:debian:oldstable
buildx failed with: ERROR: failed to solve: registry.community.greenbone.net/community/gvm-libs:edge: failed to resolve source metadata for registry.community.greenbone.net/community/gvm-libs:edge: unexpected status from HEAD request to https://registry.community.greenbone.net/v2/community/gvm-libs/manifests/edge: 502 Bad Gateway
|
container / greenbone-reg:debian:stable / build-amd64
Process "docker run" closed with code 1
|
container / ghcr:debian:oldstable
Process "docker run" closed with code 1
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
.docker/prod.Dockerfile#L72
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
.docker/prod.Dockerfile#L72
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
.docker/prod.Dockerfile#L72
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
functional / tests
Restore cache failed: Dependencies file is not found in /__w/openvas-scanner/openvas-scanner. Supported file pattern: go.sum
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
greenbone~openvas-scanner~P0PU6H.dockerbuild
Expired
|
91.5 KB |
|
greenbone~openvas-scanner~QE0GYW.dockerbuild
Expired
|
94 KB |
|
greenbone~openvas-scanner~TP3FJB.dockerbuild
Expired
|
91.1 KB |
|
openvas-scanner.sarif
Expired
|
86.4 KB |
|
ovimage
Expired
|
260 MB |
|
rs-binaries
Expired
|
19.9 MB |
|