GRIF-683: Fixing invalid ascii characters in LCM bricks parameters #336
hung-nguyen-hoangcheck.yaml
on: pull_request
prepare-env
1m 1s
gooddata-ruby-lcm-build-pipeline
/
prepare-build
15s
gooddata-ruby-fossa-licenses-validate-LR-ticket-zuul
5s
Matrix: gooddata-ruby-lcm-build-pipeline / charts-validation
Waiting for pending jobs
Matrix: gooddata-ruby-lcm-build-pipeline / dockerfiles-validation
Matrix: gooddata-ruby-lcm-build-pipeline / helm-charts-build
Matrix: gooddata-ruby-lcm-build-pipeline / services-build
gooddata-ruby-lcm-build-pipeline
/
register-bricks-staging
gooddata-ruby-lcm-build-pipeline
/
...
/
build-helmreleases
gooddata-ruby-lcm-build-pipeline
/
...
/
create-gitops-deployments-pr
Matrix: gooddata-ruby-lcm-build-pipeline / wait-for-deployment
Waiting for pending jobs
gooddata-ruby-lcm-build-pipeline
/
...
/
promote-to-stable
gooddata-ruby-lcm-build-pipeline
/
...
/
revert-staging-pr
Matrix: gooddata-ruby-lcm-build-pipeline / register-bricks-prod
Matrix: gooddata-ruby-lcm-build-pipeline / create-auto-merge-prod-pr
Waiting for pending jobs
gooddata-ruby-lcm-build-pipeline
/
...
/
create-gitops-deployments-pr
gooddata-ruby-lcm-build-pipeline
/
...
/
create-comment-with-pr-urls
ready-to-merge
3s
Annotations
5 errors
|
gooddata-ruby-lcm-build-pipeline / services-build (lcm-bricks)
Canceling since a higher priority waiting request for check-refs/pull/2070/merge exists
|
|
gooddata-ruby-lcm-build-pipeline / services-build (lcm-bricks)
The operation was canceled.
|
|
ready-to-merge
Process completed with exit code 1.
|
|
check
Canceling since a higher priority waiting request for check-refs/pull/2070/merge exists
|
|
check
Canceling since a higher priority waiting request for check-refs/pull/2070/merge exists
|