Skip to content

DPC - Build and Deploy #9

DPC - Build and Deploy

DPC - Build and Deploy #9

Triggered via schedule February 13, 2025 06:02
Status Success
Total duration 1h 19m 52s
Artifacts 7

ecs-release.yml

on: schedule
Set Parameters
11s
Set Parameters
Matrix: Build Images / docker_build_rails_apps
Build Images  /  generate_docker_tag
2s
Build Images / generate_docker_tag
Build Images  /  docker_build_java
44m 43s
Build Images / docker_build_java
Matrix: Build Images / docker_push_all_apps
deploy  /  ...  /  Wait for dpc-api to be healthy
9m 24s
deploy / All Services Healthy / Wait for dpc-api to be healthy
deploy  /  ...  /  Wait for dpc-attribution to be healthy
11m 39s
deploy / All Services Healthy / Wait for dpc-attribution to be healthy
deploy  /  ...  /  Wait for dpc-aggregation to be healthy
10m 35s
deploy / All Services Healthy / Wait for dpc-aggregation to be healthy
deploy  /  ...  /  Wait for dpc-consent to be healthy
11m 10s
deploy / All Services Healthy / Wait for dpc-consent to be healthy
deploy  /  ...  /  Wait for dpc-web to be healthy
8m 17s
deploy / All Services Healthy / Wait for dpc-web to be healthy
deploy  /  ...  /  Wait for dpc-web sidekiq to be healthy
5m 49s
deploy / All Services Healthy / Wait for dpc-web sidekiq to be healthy
deploy  /  ...  /  Wait for dpc-admin to be healthy
6m 4s
deploy / All Services Healthy / Wait for dpc-admin to be healthy
deploy  /  ...  /  Wait for dpc-admin sidekiq to be healthy
8m 14s
deploy / All Services Healthy / Wait for dpc-admin sidekiq to be healthy
deploy  /  ...  /  Wait for dpc-portal to be healthy
4m 50s
deploy / All Services Healthy / Wait for dpc-portal to be healthy
deploy  /  ...  /  Wait for dpc-portal sidekiq to be healthy
6m 38s
deploy / All Services Healthy / Wait for dpc-portal sidekiq to be healthy
deploy  /  Notify New Relic
26s
deploy / Notify New Relic
smoke-test  /  Smoke Test
12m 1s
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
367 MB
dpc-api Expired
396 MB
dpc-attribution Expired
360 MB
dpc-consent Expired
360 MB
dpc-web Expired
144 MB
dpc-web-admin Expired
139 MB
dpc-web-portal Expired
467 MB