Skip to content

PTFE-1981 handle cancelled build on same sha #588

PTFE-1981 handle cancelled build on same sha

PTFE-1981 handle cancelled build on same sha #588

Triggered via push October 11, 2024 22:23
Status Failure
Total duration 1m 9s
Artifacts 1

build.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
scan / analyse
Bad request - jaxxstorm/[email protected] is not allowed to be used in scality/bert-e. Actions in this workflow must be: within a repository that belongs to your Enterprise account, created by GitHub, verified in the GitHub Marketplace, or matching the following: crazy-max/ghaction-github-labeler@*, dependabot/*, engineerd/setup-kind@*, gabrielbb/xvfb-action@*, golangci/golangci-lint-action@*, peaceiris/actions-gh-pages@*, pypa/*, release-drafter/release-drafter@*, salsify/action-detect-and-tag-new-version@*, softprops/action-gh-release@*, ncipollo/release-action@*, peter-evans/create-pull-request@*, brettcannon/check-for-changed-files@*, ad-m/github-push-action@*, tj-actions/changed-files@*, tj-actions/glob@*, actions-cool/maintain-one-comment@*, tj-actions/json2file@*, easingthemes/ssh-deploy@*, peter-murray/github-security-report-action@*, runforesight/workflow-telemetry-action@*, miniscruff/changie-action@*, helm/kind-action@*, ppremk/lfs-warning@*, charpi/jira-release-actions...
Legacy key/value format with whitespace separator should not be used: Dockerfile#L7
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/

Artifacts

Produced during runtime
Name Size
scality~bert-e~UGXJO7.dockerbuild
40.5 KB