Skip to content
CI/CD Main

fix(graphql): Set max execution depth to allow inspection query (#1679) #958

Sign in to view logs

fix(graphql): Set max execution depth to allow inspection query (#1679)

fix(graphql): Set max execution depth to allow inspection query (#1679) #958

Re-run triggered January 14, 2025 08:30
@arealmaasarealmaas
6265110
main
Status Failure
Total duration 3m 16s
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
5s
Generate git short sha / Generate git short sha
Get current version  /  Filter
3s
Get current version / Filter
Release please
35s
Release please
Build and test backend  /  build-and-test
1m 34s
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
Run K6 functional end-to-end tests / k6-test
Deploy schema npm package  /  check-published-version
Deploy schema npm package / check-published-version
Deploy schema npm package  /  publish-schema-to-npm
Deploy schema npm package / publish-schema-to-npm
Send Slack message on failure  /  Send Slack message
4s
Send Slack message on failure / Send Slack message
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 19 warnings
Deploy apps to test / Deploy web-api-so to test
Error: az cli script failed.
Deploy apps to test / Deploy web-api-so to test
az cli script failed.
Deploy apps to test / Deploy web-api-eu to test
The job was canceled because "web-api-so" failed.
Deploy apps to test / Deploy web-api-eu to test
The operation was canceled.
Release please
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Generate git short sha / Generate git short sha
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Check for changes / Filter
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Get current version / Filter
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and test backend / build-and-test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and publish docker images / publish-docker-images (./src/Digdir.Domain.Dialogporten.GraphQL/Dockerfile, graphql)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and publish docker images / publish-docker-images (./src/Digdir.Domain.Dialogporten.WebApi/Dockerfile, webapi)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and publish docker images / publish-docker-images (./src/Digdir.Domain.Dialogporten.Infrastructure/MigrationBundle.dockerfile...
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/
Build and publish docker images / publish-docker-images (./src/Digdir.Domain.Dialogporten.ChangeDataCapture/Dockerfile, cdc)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and publish docker images / publish-docker-images (./src/Digdir.Domain.Dialogporten.Service/Dockerfile, service)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and publish docker images / publish-docker-images (./src/Digdir.Domain.Dialogporten.Janitor/Dockerfile, janitor)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy apps to test / Deploy service to test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy apps to test / Deploy graphql to test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy apps to test / Deploy web-api-so to test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Send Slack message on failure / Send Slack message
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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).