Skip to content

Add "service" field in bans when sending it to the API from bwcli #2999

Add "service" field in bans when sending it to the API from bwcli

Add "service" field in bans when sending it to the API from bwcli #2999

Triggered via push October 23, 2024 09:44
Status Failure
Total duration 9m 32s
Artifacts 20

dev.yml

on: push
Matrix: build-containers
Matrix: build-packages
Matrix: codeql / code-security
Matrix: push-packages
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

1 error and 30 warnings
build-packages (rhel) / build
Failed to CreateArtifact: Failed to make request after 5 attempts: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact
build-containers (ui) / build
The process '/usr/bin/git' failed with exit code 128
build-containers (scheduler) / build
The process '/usr/bin/git' failed with exit code 128
build-containers (autoconf) / build
The process '/usr/bin/git' failed with exit code 128
codeql / code-security (javascript)
The process '/usr/bin/git' failed with exit code 128
codeql / code-security (javascript)
The setup-python-dependencies input is deprecated and no longer has any effect. We recommend removing any references from your workflows. See https://github.blog/changelog/2024-01-23-codeql-2-16-python-dependency-installation-disabled-new-queries-and-bug-fixes/ for more information.
codeql / code-security (python)
The setup-python-dependencies input is deprecated and no longer has any effect. We recommend removing any references from your workflows. See https://github.blog/changelog/2024-01-23-codeql-2-16-python-dependency-installation-disabled-new-queries-and-bug-fixes/ for more information.
codeql / code-security (python)
The CODEQL_PYTHON environment variable is no longer supported. Please remove it from your workflow. This environment variable was originally used to specify a Python executable that included the dependencies of your Python code, however Python analysis no longer uses these dependencies. If you used CODEQL_PYTHON to force the version of Python to analyze as, please use CODEQL_EXTRACTOR_PYTHON_ANALYSIS_VERSION instead, such as 'CODEQL_EXTRACTOR_PYTHON_ANALYSIS_VERSION=2.7' or 'CODEQL_EXTRACTOR_PYTHON_ANALYSIS_VERSION=3.11'.
codeql / code-security (python)
The process '/usr/bin/git' failed with exit code 128
build-containers (bunkerweb) / build
The process '/usr/bin/git' failed with exit code 128
Legacy key/value format with whitespace separator should not be used: tests/linux/Dockerfile-ubuntu-jammy#L6
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: tests/linux/Dockerfile-ubuntu-jammy#L3
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: tests/linux/Dockerfile-ubuntu-jammy#L4
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: tests/linux/Dockerfile-ubuntu-jammy#L5
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-packages (ubuntu-jammy) / build
The process '/usr/bin/git' failed with exit code 128
build-packages (debian) / build
The process '/usr/bin/git' failed with exit code 128
Legacy key/value format with whitespace separator should not be used: tests/linux/Dockerfile-debian#L4
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: tests/linux/Dockerfile-debian#L5
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: tests/linux/Dockerfile-debian#L6
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: tests/linux/Dockerfile-debian#L3
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-packages (ubuntu) / build
The process '/usr/bin/git' failed with exit code 128
Legacy key/value format with whitespace separator should not be used: tests/linux/Dockerfile-ubuntu#L5
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: tests/linux/Dockerfile-ubuntu#L6
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: tests/linux/Dockerfile-ubuntu#L3
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: tests/linux/Dockerfile-ubuntu#L4
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-packages (rhel9) / build
The process '/usr/bin/git' failed with exit code 128
Legacy key/value format with whitespace separator should not be used: tests/linux/Dockerfile-rhel9#L3
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: tests/linux/Dockerfile-fedora#L3
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: tests/linux/Dockerfile-fedora#L4
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-packages (fedora) / build
The process '/usr/bin/git' failed with exit code 128
build-packages (rhel) / build
The process '/usr/bin/git' failed with exit code 128

Artifacts

Produced during runtime
Name Size
bunkerity~bunkerweb~0YJNOK.dockerbuild Expired
107 KB
bunkerity~bunkerweb~C97CZ3.dockerbuild Expired
109 KB
bunkerity~bunkerweb~EDCTLC.dockerbuild Expired
102 KB
bunkerity~bunkerweb~IDWN4T.dockerbuild Expired
93.9 KB
bunkerity~bunkerweb~K1N7UT.dockerbuild Expired
106 KB
bunkerity~bunkerweb~LP61ZD.dockerbuild Expired
32.3 KB
bunkerity~bunkerweb~NB9ZA4.dockerbuild Expired
53.8 KB
bunkerity~bunkerweb~O726X1.dockerbuild Expired
104 KB
bunkerity~bunkerweb~QV498B.dockerbuild Expired
49.6 KB
bunkerity~bunkerweb~R2H4VR.dockerbuild Expired
35.9 KB
bunkerity~bunkerweb~RB39SR.dockerbuild Expired
30.9 KB
bunkerity~bunkerweb~TI4JEN.dockerbuild Expired
29.4 KB
bunkerity~bunkerweb~W6AFFF.dockerbuild Expired
29.3 KB
bunkerity~bunkerweb~WJK272.dockerbuild Expired
57.6 KB
bunkerity~bunkerweb~ZGFPLJ.dockerbuild Expired
32.8 KB
package-debian-amd64 Expired
77 MB
package-fedora-x86_64 Expired
73.5 MB
package-rhel9-x86_64 Expired
70.6 MB
package-ubuntu-amd64 Expired
76.4 MB
package-ubuntu-jammy-amd64 Expired
72.3 MB