Skip to content

CI: [pull] develop from baserow:develop #477

CI: [pull] develop from baserow:develop

CI: [pull] develop from baserow:develop #477

Triggered via pull request May 5, 2026 20:01
Status Cancelled
Total duration 2d 10h 58m 30s
Artifacts 3

ci.yml

on: pull_request
Check build and publish
4s
Check build and publish
Detect Changed Files
12s
Detect Changed Files
Build Backend CI Image
3m 15s
Build Backend CI Image
Build Web-Frontend CI Image
6m 46s
Build Web-Frontend CI Image
Dockerfile Lint (hadolint)
0s
Dockerfile Lint (hadolint)
Helm Chart Lint
0s
Helm Chart Lint
Zapier Integration Tests
0s
Zapier Integration Tests
Check MJML Email Templates Compiled
0s
Check MJML Email Templates Compiled
Backend Startup Check
1d 0h
Backend Startup Check
Matrix: test-e2e
Matrix: test-frontend
Web-Frontend Lint
1d 0h
Web-Frontend Lint
Matrix: test-backend
Collect E2E Test Reports
0s
Collect E2E Test Reports
Build Final Web-Frontend Image
0s
Build Final Web-Frontend Image
Build Final Backend Image
0s
Build Final Backend Image
Collect Backend Coverage
0s
Collect Backend Coverage
Publish develop-latest web-frontend image
Publish develop-latest web-frontend image
Build All-in-One Image
Build All-in-One Image
Publish develop-latest backend image
0s
Publish develop-latest backend image
CI Status
2s
CI Status
Build Cloudron Image
Build Cloudron Image
Publish develop-latest all-in-one image
Publish develop-latest all-in-one image
Trigger SaaS GitLab Pipeline
Trigger SaaS GitLab Pipeline
Publish develop-latest Cloudron image
0s
Publish develop-latest Cloudron image
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 6 warnings
Backend Lint
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Backend Startup Check
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
E2E Tests (Shard 1)
Unable to download artifact(s): Artifact not found for name: backend-ci-image Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
E2E Tests (Shard 2)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Web-Frontend Lint
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Web-Frontend Tests (Shard 3)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Web-Frontend Tests (Shard 1)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
CI Status
Process completed with exit code 1.
Detect Changed Files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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/
Build Backend CI Image
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/upload-artifact@v4, docker/build-push-action@v5, docker/setup-buildx-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/
Build Web-Frontend CI Image
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/upload-artifact@v4, docker/build-push-action@v5, docker/setup-buildx-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/
E2E Tests (Shard 1)
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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@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/
E2E Tests (Shard 1)
No files were found with the provided path: e2e-tests/blob-report/. No artifacts will be uploaded.
Web-Frontend Tests (Shard 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/upload-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
backend-ci-image Expired
390 MB
sha256:be6a00074644fb743af5286478bce42fc0595eda2c6a13b4fe42b4d8db3d0324
frontend-ci-image Expired
326 MB
sha256:086c7cad09b3f0502b62ced03d6312b898346a505a9f3f5095857e66368f320a
web-frontend-test-reports-shard-2 Expired
47.5 KB
sha256:4305ce152b4fbc6d35820e466e7a122e843b44897e49a888067e23e33d595778