Skip to content

Content release: Dev #67

Content release: Dev

Content release: Dev #67

Triggered via schedule November 11, 2024 09:10
Status Failure
Total duration 1h 1m 58s
Artifacts
content-release-dev  /  Validate Build Status
1m 0s
content-release-dev / Validate Build Status
content-release-dev  /  login-to-amazon-ecr
5s
content-release-dev / login-to-amazon-ecr
content-release-dev  /  Notify Start (Slack)
18s
content-release-dev / Notify Start (Slack)
content-release-dev  /  Build static pages & deploy to S3
1h 0m
content-release-dev / Build static pages & deploy to S3
content-release-dev  /  Record metrics in Datadog
0s
content-release-dev / Record metrics in Datadog
content-release-dev  /  Notify Failure
26s
content-release-dev / Notify Failure
content-release-dev  /  Notify Success
0s
content-release-dev / Notify Success
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
content-release-dev / Build static pages & deploy to S3
The job running on runner K3B5M9i-0a36ffa10fbc6d934 has exceeded the maximum execution time of 60 minutes.
content-release-dev / Build static pages & deploy to S3
The operation was canceled.
content-release-dev / login-to-amazon-ecr
Your docker password is not masked. See https://github.com/aws-actions/amazon-ecr-login#docker-credentials for more information.
content-release-dev / Notify Start (Slack)
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2, slackapi/slack-github-action@v1.23.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
content-release-dev / Notify Failure
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2, slackapi/slack-github-action@v1.23.0, department-of-veterans-affairs/action-inject-ssm-secrets@d8e6de3bde4dd728c9d732baef58b3c854b8c4bb. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/