Support recoverability for Azure ServiceBus dead letter messages #8735
andreasohlundci.yml
on: pull_request
Matrix: containers / containers
db-container
/
db-container
1m 2s
windows-installers
/
build
2m 10s
Matrix: build
Matrix: container-test / container-test
Waiting for pending jobs
Annotations
24 errors and 4 warnings
|
Linux-RabbitMQ
Process completed with exit code 1.
|
|
Linux-Default
Process completed with exit code 1.
|
|
Linux-SQS
Process completed with exit code 1.
|
|
Linux-PrimaryRavenAcceptance
Process completed with exit code 1.
|
|
Linux-PostgreSQL
Process completed with exit code 1.
|
|
Linux-AzureStorageQueues
Process completed with exit code 1.
|
|
containers / servicecontrol-monitoring
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c dotnet build src/ServiceControl.Monitoring/ServiceControl.Monitoring.csproj --configuration Release -graph --property:TargetArch=$TARGETARCH" did not complete successfully: exit code: 1
|
|
Linux-IBMMQ
Process completed with exit code 1.
|
|
Linux-PrimaryRavenPersistence
Process completed with exit code 1.
|
|
containers / servicecontrol
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c dotnet build src/ServiceControl/ServiceControl.csproj --configuration Release -graph --property:TargetArch=$TARGETARCH" did not complete successfully: exit code: 1
|
|
Linux-AzureServiceBus
Process completed with exit code 1.
|
|
containers / servicecontrol-audit
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c dotnet build src/ServiceControl.Audit/ServiceControl.Audit.csproj --configuration Release -graph --property:TargetArch=$TARGETARCH" did not complete successfully: exit code: 1
|
|
Linux-SqlServer
Process completed with exit code 1.
|
|
Windows-AzureServiceBus
Process completed with exit code 1.
|
|
Windows-SQS
Process completed with exit code 1.
|
|
Windows-SqlServer
Process completed with exit code 1.
|
|
Windows-RabbitMQ
Process completed with exit code 1.
|
|
windows-installers / build
Process completed with exit code 1.
|
|
Windows-MSMQ
Process completed with exit code 1.
|
|
Windows-PrimaryRavenAcceptance
Process completed with exit code 1.
|
|
Windows-AzureStorageQueues
Process completed with exit code 1.
|
|
Windows-PrimaryRavenPersistence
Process completed with exit code 1.
|
|
Windows-PostgreSQL
Process completed with exit code 1.
|
|
Windows-Default
Process completed with exit code 1.
|
|
containers / servicecontrol-monitoring
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
containers / servicecontrol
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
db-container / db-container
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
containers / servicecontrol-audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Particular~ServiceControl~9JUBMF.dockerbuild
|
41 KB |
sha256:96cc7e634ca679f1e58be98b8fa545f5a094dd10af2cb424e9b98b1e3318b2ff
|
|
|
Particular~ServiceControl~GZ58AX.dockerbuild
|
40.2 KB |
sha256:68a85545cba93b652e245d7a5df70d02007e7e065c8fa6b0f60f551086ce3adb
|
|
|
Particular~ServiceControl~UIX6LY.dockerbuild
|
41.5 KB |
sha256:edaaa3bb37aada81c5173d90f3f0b3cfcc1f495be541a2c20263bb793e79b75f
|
|