Skip to content

.github/workflows/release.yml #81

.github/workflows/release.yml

.github/workflows/release.yml #81

Triggered via push September 1, 2024 22:30
Status Failure
Total duration 8m 7s
Artifacts 4

release.yml

on: push
Matrix: build / build-desktop-windows
build  /  build-docker-server
4m 4s
build / build-docker-server
build  /  build-docker-jobrunner
2m 41s
build / build-docker-jobrunner
test-e2e-server
4s
test-e2e-server
test-desktop
9s
test-desktop
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
markspolakovs
approved Sep 1, 2024
release

Annotations

1 error and 6 warnings
release
Unhandled error: SyntaxError: Invalid or unexpected token
Sensitive data should not be used in the ARG or ENV commands: Dockerfile.jobrunner#L22
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_AUTH_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile.jobrunner#L23
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SENTRY_AUTH_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile.server#L24
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_AUTH_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile.server#L25
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SENTRY_AUTH_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
linear
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
badger-desktop-windows Expired
155 MB
badger-desktop-windows-ystv Expired
155 MB
ystv~badger~04FUAQ.dockerbuild Expired
36.4 KB
ystv~badger~709ZTL.dockerbuild Expired
34.1 KB