Update test workflow to use push trigger (workflow_dispatch requires … #1
santos1709test-lcm-pipeline.yaml
on: push
test
/
prepare-build
25s
Matrix: test / charts-validation
Waiting for pending jobs
Matrix: test / dockerfiles-validation
test
/
notify-image-available
3s
Matrix: test / helm-charts-build
Matrix: test / services-build
Matrix: test / create-auto-merge-prod-pr
Waiting for pending jobs
test
/
...
/
create-gitops-deployments-pr
Matrix: test / wait-for-deployment
Waiting for pending jobs
test
/
...
/
create-comment-with-pr-urls
test
/
...
/
LCM-integration-e2e-tests
11m 29s
test
/
...
/
promote-to-stable
test
/
...
/
revert-staging-pr
1d 0h
Annotations
3 errors and 4 warnings
|
test / notify-image-available
Process completed with exit code 2.
|
|
test / lcm-integration-e2e / LCM-integration-e2e-tests
Process completed with exit code 1.
|
|
test / revert-staging-pr / revert-staging-pr
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test / 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/
|
|
test / 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/
|
|
test / 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/
|
|
test / lcm-integration-e2e / LCM-integration-e2e-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|