deploy-frontends-to-staging

Website2 deployment1 #1278

Sign in to view logs

Re-run triggered November 19, 2024 10:15

Psalmz777

#2241

Website2-deployment1

Status Failure

Total duration 2m 53s

Artifacts –

deploy-frontends-to-staging.yml

on: pull_request

create image tag

check for changed frontends

build-push-netmanager-image

build-push-deploy-website

build-push-deploy-website2

build-push-calibrate-app-image

build-push-analytics-platform-image

build-push-docs-image

build-push-inventory-image

build-push-reports-image

Annotations

1 error and 4 warnings

build-push-deploy-website2

Process completed with exit code 1.

check for changed frontends

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

build-push-deploy-website2

The following actions uses node12 which is deprecated and will be forced to run on node16: jsdaniell/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

build-push-deploy-website2

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/login-action@v2, google-github-actions/auth@v1, google-github-actions/setup-gcloud@v1, jsdaniell/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

build-push-deploy-website2

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/