Skip to content

GRIF-716: Improve LCM brick post merge roll out #375

GRIF-716: Improve LCM brick post merge roll out

GRIF-716: Improve LCM brick post merge roll out #375

Triggered via pull request May 21, 2026 16:48
Status Cancelled
Total duration 10m 23s
Artifacts

check.yaml

on: pull_request
prepare-env
47s
prepare-env
gooddata-ruby-lcm-build-pipeline  /  prepare-build
11s
gooddata-ruby-lcm-build-pipeline / prepare-build
gooddata-ruby-fossa-licenses-validate-LR-ticket-zuul
5s
gooddata-ruby-fossa-licenses-validate-LR-ticket-zuul
Matrix: gooddata-ruby-lcm-build-pipeline / charts-validation
Waiting for pending jobs
Matrix: gooddata-ruby-lcm-build-pipeline / dockerfiles-validation
gooddata-ruby-lcm-build-pipeline  /  notify-image-available
0s
gooddata-ruby-lcm-build-pipeline / notify-image-available
Matrix: gooddata-ruby-lcm-build-pipeline / helm-charts-build
Matrix: gooddata-ruby-lcm-build-pipeline / services-build
gooddata-ruby-lcm-build-pipeline  /  ...  /  build-helmreleases
gooddata-ruby-lcm-build-pipeline / build-helmreleases / build-helmreleases
gooddata-ruby-lcm-build-pipeline  /  ...  /  create-gitops-deployments-pr
gooddata-ruby-lcm-build-pipeline / create-staging-pr / create-gitops-deployments-pr
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-manual-merge-prod-pr / create-gitops-deployments-pr
Matrix: gooddata-ruby-lcm-build-pipeline / wait-for-deployment
Waiting for pending jobs
gooddata-ruby-lcm-build-pipeline  /  ...  /  create-comment-with-pr-urls
gooddata-ruby-lcm-build-pipeline / create-comment-with-pr-urls / create-comment-with-pr-urls
gooddata-ruby-lcm-build-pipeline  /  ...  /  LCM-integration-e2e-tests
gooddata-ruby-lcm-build-pipeline / lcm-integration-e2e / LCM-integration-e2e-tests
gooddata-ruby-lcm-build-pipeline  /  ...  /  promote-to-stable
gooddata-ruby-lcm-build-pipeline / promote-to-stable / promote-to-stable
gooddata-ruby-lcm-build-pipeline  /  ...  /  revert-staging-pr
gooddata-ruby-lcm-build-pipeline / revert-staging-pr / revert-staging-pr
ready-to-merge
3s
ready-to-merge
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 4 warnings
gooddata-ruby-lcm-build-pipeline / services-build (lcm-bricks)
Canceling since a higher priority waiting request for check-refs/pull/2079/merge exists
gooddata-ruby-lcm-build-pipeline / services-build (lcm-bricks)
The operation was canceled.
check
Canceling since a higher priority waiting request for check-refs/pull/2079/merge exists
check
Canceling since a higher priority waiting request for check-refs/pull/2079/merge exists
ready-to-merge
Process completed with exit code 1.
prepare-env
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, tj-actions/changed-files@v45. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
gooddata-ruby-lcm-build-pipeline / prepare-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
gooddata-ruby-lcm-build-pipeline / services-build (lcm-bricks-nextversion)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4, hashicorp/vault-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
gooddata-ruby-lcm-build-pipeline / services-build (lcm-bricks)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4, hashicorp/vault-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/