CI/CD YT01 (1.50.3) #84
Triggered via repository dispatch
February 12, 2025 14:51
dialogporten-bot
dialogporten-bot
release_created
305d945
Status
Failure
Total duration
16m 40s
Artifacts
1
ci-cd-yt01.yml
on: repository_dispatch
Get Latest Deployed Version Info from GitHub
/
Get Latest Deployed Versions from GitHub Variables
4s
Deploy apps to yt01
/
Deploy migration job to yt01
2m 11s
Store Latest Deployed Infra Version as GitHub Variable
/
Store GitHub Environment Variable
5s
Matrix: Deploy apps to yt01 / deploy-apps
Matrix: Deploy apps to yt01 / deploy-jobs
Matrix: Run K6 performance tests
Store Latest Deployed Apps Version as GitHub Variable
/
Store GitHub Environment Variable
Send Slack message on failure
/
Send Slack message
4s
Annotations
3 errors and 5 warnings
|
Run K6 performance tests (tests/k6/tests/serviceowner/performance/serviceOwnerSearchWithThreshold... / k6-test
Process completed with exit code 99.
|
|
Run K6 functional end-to-end tests / k6-test
This action finished successfully, but test results have status failure.
|
|
Run K6 performance tests (tests/k6/tests/enduser/performance/enduserSearchWithThresholds.js) / k6-test
Process completed with exit code 99.
|
|
Deploy infra to yt01 / Deploy to yt01
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Deploy infra to yt01 / Deploy to yt01
This deployment mode is not supported for subscription scoped deployments, this parameter will be ignored!
|
|
Deploy infra to yt01 / Deploy to yt01
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Send Slack message on failure / Send Slack message
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.
|
|
Send Slack message on failure / Send Slack message
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 | |
|---|---|---|
|
k6-summary-report
|
2.56 KB |
|