Skip to content

DPC - Build and Deploy #53

DPC - Build and Deploy

DPC - Build and Deploy #53

Triggered via schedule March 6, 2025 06:01
Status Success
Total duration 1h 32m 29s
Artifacts 7

ecs-release.yml

on: schedule
Set Parameters
10s
Set Parameters
Matrix: Build Images / docker_build_rails_apps
Build Images  /  generate_docker_tag
20s
Build Images / generate_docker_tag
Build Images  /  docker_build_java
59m 26s
Build Images / docker_build_java
Matrix: Build Images / docker_push_all_apps
Matrix: deploy / All Services Healthy / Wait for services to be healthy
deploy  /  Notify New Relic
33s
deploy / Notify New Relic
deploy  /  Notify Slack
3s
deploy / Notify Slack
smoke-test  /  Smoke Test
8m 44s
smoke-test / Smoke Test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
smoke-test / Smoke Test
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
smoke-test / Smoke Test
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
smoke-test / Smoke Test
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
smoke-test / Smoke Test
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).

Artifacts

Produced during runtime
Name Size
dpc-aggregation Expired
389 MB
dpc-api Expired
414 MB
dpc-attribution Expired
380 MB
dpc-consent Expired
381 MB
dpc-web Expired
144 MB
dpc-web-admin Expired
140 MB
dpc-web-portal Expired
465 MB