Skip to content

chore(deps): update dotnet monorepo (#1961) #1166

chore(deps): update dotnet monorepo (#1961)

chore(deps): update dotnet monorepo (#1961) #1166

Triggered via push February 26, 2025 08:16
Status Failure
Total duration 10m 39s
Artifacts 6

ci-cd-main.yml

on: push
Check for changes  /  Filter
3s
Check for changes / Filter
Generate git short sha  /  Generate git short sha
4s
Generate git short sha / Generate git short sha
Get current version  /  Filter
2s
Get current version / Filter
Generate timestamp
4s
Generate timestamp
Build and test backend  /  build-and-test
1m 38s
Build and test backend / build-and-test
Deploy infra to test  /  deploy
Deploy infra to test / deploy
Matrix: Build and publish docker images / publish-docker-images
Deploy apps to test  /  Deploy migration job to ${{ inputs.environment }}
0s
Deploy apps to test / Deploy migration job to ${{ inputs.environment }}
Matrix: Deploy apps to test / deploy-apps
Matrix: Deploy apps to test / deploy-jobs
Run K6 functional end-to-end tests  /  k6-test
1m 42s
Run K6 functional end-to-end tests / k6-test
Deploy schema npm package  /  check-published-version
Deploy schema npm package / check-published-version
publish-sdk-to-nuget  /  build-and-push
publish-sdk-to-nuget / build-and-push
Deploy schema npm package  /  publish-schema-to-npm
Deploy schema npm package / publish-schema-to-npm
Send Slack message on failure  /  Send Slack message
3s
Send Slack message on failure / Send Slack message
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
Run K6 functional end-to-end tests / k6-test
This action finished successfully, but test results have status failure.
Legacy key/value format with whitespace separator should not be used: src/Digdir.Domain.Dialogporten.Infrastructure/MigrationBundle.dockerfile#L8
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: src/Digdir.Domain.Dialogporten.Infrastructure/MigrationBundle.dockerfile#L33
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
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
Altinn~dialogporten~HY7CQT.dockerbuild
65.1 KB
Altinn~dialogporten~KNQRFY.dockerbuild
61.9 KB
Altinn~dialogporten~U75H7F.dockerbuild
70.3 KB
Altinn~dialogporten~WN6UWC.dockerbuild
67.2 KB
Altinn~dialogporten~WQJB3F.dockerbuild
65.6 KB
k6-summary-report
6.04 KB