DPC-5222 re-enable portal smoke test at new subdomain (#2936) #752
jdettmannnavaecs-release.yml
on: push
Validate Parameters
3s
Matrix: Build Images / docker_build_rails_apps
Build Images
/
generate_docker_tag
10s
Build Images
/
docker_build_java
25m 12s
Matrix: Build Images / docker_push_all_apps
Matrix: deploy / All Services Healthy / Wait for services to be healthy
smoke-test
/
Smoke Test
5m 47s
Annotations
4 warnings
|
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).
|
|
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.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
dpc-aggregation
Expired
|
414 MB |
sha256:a083fe0892ab978146213e03af5676cfbafdc784410a35eaca4af3d711d47745
|
|
|
dpc-api
Expired
|
415 MB |
sha256:1a0bdc5223ad234d88dbbf9e492713220ee21f4726dbdecc3cfbaf2dc35cbeb2
|
|
|
dpc-attribution
Expired
|
395 MB |
sha256:1348eab37f60a5d2844b04ed9664b43ffc736606a4de611ef588614c83d8ba88
|
|
|
dpc-web
Expired
|
148 MB |
sha256:661e033f25618f81e2265b4a234d0b38f53950865c2471d39230c5bc74b4110a
|
|
|
dpc-web-admin
Expired
|
140 MB |
sha256:0561820e058898f2dc4f4b5efd0d9a66417c05f3f9ca1e1af4bad0171c02f362
|
|
|
dpc-web-portal
Expired
|
487 MB |
sha256:b11f3f584072cad6c4e2aef64ddb451316d722a0413085119a574bb7ecd728de
|
|