Skip to content

[DPC-4550] Foundational code for load tests (#2504) #55

[DPC-4550] Foundational code for load tests (#2504)

[DPC-4550] Foundational code for load tests (#2504) #55

Triggered via push March 7, 2025 14:48
Status Success
Total duration 1h 18m 23s
Artifacts 7

ecs-release.yml

on: push
Set Parameters
11s
Set Parameters
Matrix: Build Images / docker_build_rails_apps
Build Images  /  generate_docker_tag
4s
Build Images / generate_docker_tag
Build Images  /  docker_build_java
45m 2s
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
25s
deploy / Notify New Relic
deploy  /  Notify Slack
4s
deploy / Notify Slack
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