Reject usage reports with incorrect duration and errorsTotal values #18123
kamilkisielapr.yaml
on: pull_request
Matrix: build / build-and-dockerize
db-types
/
diff
1m 19s
test
/
db-migrations
1m 19s
test
/
unit
1m 54s
code-style
/
eslint-and-prettier
2m 12s
typescript
/
typecheck
4m 34s
website-preview
/
deployment
5s
storybook-preview
/
deployment
9s
release-candidate
/
snapshot
Matrix: static-analysis / analyze
Matrix: alpha / cli-test
Annotations
5 errors and 29 warnings
|
code-style / eslint-and-prettier
Process completed with exit code 1.
|
|
test / integration (1)
The run was canceled by @github-actions[bot].
|
|
test / integration (2)
The run was canceled by @github-actions[bot].
|
|
test / e2e
The run was canceled by @github-actions[bot].
|
|
test / integration (3)
The run was canceled by @github-actions[bot].
|
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
static-analysis / analyze (typescript)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
static-analysis / analyze (typescript)
Unable to validate code scanning workflow: MissingPushHook
|
|
static-analysis / analyze (javascript)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
static-analysis / analyze (javascript)
Unable to validate code scanning workflow: MissingPushHook
|
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L11
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/
|
|
Variables should be defined before their use:
docker/migrations.dockerfile#L15
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L12
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L13
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L14
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L20
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/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L21
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
docker/migrations.dockerfile#L12
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L12
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/services.dockerfile#L21
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/services.dockerfile#L22
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/migrations.dockerfile#L10
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/migrations.dockerfile#L12
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/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L14
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L21
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/
|
|
Variables should be defined before their use:
docker/migrations.dockerfile#L12
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
docker/migrations.dockerfile#L17
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L13
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L11
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/
|
|
Variables should be defined before their use:
docker/services.dockerfile#L21
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
graphql-hive~console~QCF7BA+13.dockerbuild
|
1.34 MB |
|
|
graphql-hive~console~Z172ZT+13.dockerbuild
|
1.3 MB |
|
|
hive-cli-darwin-arm64
|
41.9 MB |
|
|
hive-cli-darwin-x64
|
42.5 MB |
|
|
hive-cli-linux-arm
|
42.4 MB |
|
|
hive-cli-linux-x64
|
47.3 MB |
|
|
hive-cli-win-x64
|
37.5 MB |
|
|
hive-cli-win-x86
|
34.9 MB |
|