Skip to content

fix: preserve docker compose env vars during sudo deploy #5

fix: preserve docker compose env vars during sudo deploy

fix: preserve docker compose env vars during sudo deploy #5

Triggered via push March 26, 2026 18:13
Status Cancelled
Total duration 55s
Artifacts

cd.yml

on: push
Frontend Quality
15s
Frontend Quality
Backend Quality
51s
Backend Quality
Build And Push Images
0s
Build And Push Images
Deploy To Azure VM
0s
Deploy To Azure VM
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
Frontend Quality
Canceling since a higher priority waiting request for cd-refs/heads/main exists
Frontend Quality
The operation was canceled.
Backend Quality
Canceling since a higher priority waiting request for cd-refs/heads/main exists
CD
Canceling since a higher priority waiting request for cd-refs/heads/main exists
Frontend Quality
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, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Backend Quality
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/setup-java@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/