Skip to content

gate

gate #103

Triggered via merge group August 24, 2026 08:30
Status Failure
Total duration 3m 52s
Artifacts –

gate.yaml

on: merge_group
prepare-env
25s
prepare-env
gooddata-ruby-lcm-promote-pipeline  /  prepare-build
26s
gooddata-ruby-lcm-promote-pipeline / prepare-build
gooddata-ruby-fossa-licenses-validate-LR-ticket-zuul
4s
gooddata-ruby-fossa-licenses-validate-LR-ticket-zuul
Matrix: gooddata-ruby-lcm-promote-pipeline / charts-validation
Matrix: gooddata-ruby-lcm-promote-pipeline / dockerfiles-validation
Waiting for pending jobs
Matrix: gooddata-ruby-lcm-promote-pipeline / helm-charts-build
Matrix: gooddata-ruby-lcm-promote-pipeline / services-build
gooddata-ruby-lcm-promote-pipeline  /  register-bricks-staging
0s
gooddata-ruby-lcm-promote-pipeline / register-bricks-staging
gooddata-ruby-lcm-promote-pipeline  /  ...  /  build-helmreleases
28s
gooddata-ruby-lcm-promote-pipeline / build-helmreleases / build-helmreleases
gooddata-ruby-lcm-promote-pipeline  /  ...  /  create-gitops-deployments-pr
13s
gooddata-ruby-lcm-promote-pipeline / create-staging-pr / create-gitops-deployments-pr
Matrix: gooddata-ruby-lcm-promote-pipeline / create-auto-merge-prod-pr
Waiting for pending jobs
gooddata-ruby-lcm-promote-pipeline  /  ...  /  create-gitops-deployments-pr
16s
gooddata-ruby-lcm-promote-pipeline / create-manual-merge-prod-pr / create-gitops-deployments-pr
Matrix: gooddata-ruby-lcm-promote-pipeline / wait-for-deployment
Waiting for pending jobs
gooddata-ruby-lcm-promote-pipeline  /  ...  /  create-comment-with-pr-urls
5s
gooddata-ruby-lcm-promote-pipeline / create-comment-with-pr-urls / create-comment-with-pr-urls
gooddata-ruby-lcm-promote-pipeline  /  ...  /  LCM-integration-e2e-tests
gooddata-ruby-lcm-promote-pipeline / lcm-integration-e2e / LCM-integration-e2e-tests
gooddata-ruby-lcm-promote-pipeline  /  ...  /  promote-to-stable
gooddata-ruby-lcm-promote-pipeline / promote-to-stable / promote-to-stable
gooddata-ruby-lcm-promote-pipeline  /  ...  /  revert-staging-pr
gooddata-ruby-lcm-promote-pipeline / revert-staging-pr / revert-staging-pr
gooddata-ruby-lcm-promote-pipeline  /  notify-image-available
0s
gooddata-ruby-lcm-promote-pipeline / notify-image-available
ready-to-merge
4s
ready-to-merge
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 6 warnings
gooddata-ruby-lcm-promote-pipeline / create-staging-pr / create-gitops-deployments-pr
Error: To https://github.com/gooddata/gitops-deployments ! refs/heads/gooddata-ruby/b82b2162:refs/heads/gooddata-ruby/b82b2162 [remote rejected] (cannot lock ref 'refs/heads/gooddata-ruby/b82b2162': reference already exists) Done Pushing to https://github.com/gooddata/gitops-deployments POST git-receive-pack (663 bytes) error: failed to push some refs to 'https://github.com/gooddata/gitops-deployments'
gooddata-ruby-lcm-promote-pipeline / create-staging-pr / create-gitops-deployments-pr
Error: To https://github.com/gooddata/gitops-deployments ! refs/heads/gooddata-ruby/b82b2162:refs/heads/gooddata-ruby/b82b2162 [remote rejected] (cannot lock ref 'refs/heads/gooddata-ruby/b82b2162': reference already exists) Done Pushing to https://github.com/gooddata/gitops-deployments POST git-receive-pack (663 bytes) error: failed to push some refs to 'https://github.com/gooddata/gitops-deployments'
ready-to-merge
Process completed with exit code 1.
prepare-env
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, tj-actions/changed-files@v45. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
gooddata-ruby-lcm-promote-pipeline / prepare-build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: dorny/paths-filter@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
gooddata-ruby-lcm-promote-pipeline / helm-charts-build (lcm-bricks)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: aws-actions/configure-aws-credentials@v4, azure/setup-helm@v4, hashicorp/vault-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
gooddata-ruby-lcm-promote-pipeline / create-staging-pr / create-gitops-deployments-pr
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: EndBug/add-and-commit@v9. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
gooddata-ruby-lcm-promote-pipeline / create-manual-merge-prod-pr / create-gitops-deployments-pr
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: EndBug/add-and-commit@v9. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
gooddata-ruby-lcm-promote-pipeline / create-comment-with-pr-urls / create-comment-with-pr-urls
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/github-script@v7. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/