Skip to content

Introduce event publishing management for integration components and adjust Azure Service Bus customization to install the topics during provisioning #8823

Introduce event publishing management for integration components and adjust Azure Service Bus customization to install the topics during provisioning

Introduce event publishing management for integration components and adjust Azure Service Bus customization to install the topics during provisioning #8823

Triggered via pull request May 6, 2026 13:38
Status Failure
Total duration 18m 42s
Artifacts 8

ci.yml

on: pull_request
Matrix: containers / containers
db-container  /  db-container
1m 8s
db-container / db-container
windows-installers  /  build
5m 40s
windows-installers / build
Matrix: build
Matrix: container-test / container-test
Fit to window
Zoom out
Zoom in

Annotations

12 errors, 7 warnings, and 11 notices
Linux-PrimaryRavenAcceptance
Process completed with exit code 1.
Linux-PrimaryRavenAcceptance
Exit code = 1
Should_publish_notification: /_/src/ServiceControl.AcceptanceTests/Monitoring/ExternalIntegration/When_a_custom_check_fails.cs#L62
Assert.That(enclosedType, Is.EqualTo("ServiceControl.Contracts.CustomCheckFailed, ServiceControl.Contracts")) Expected string length 68 but was 135. Strings differ at index 68. Expected: "...led, ServiceControl.Contracts" But was: "...led, ServiceControl.Contracts, Version=5.0.0.0, Culture=ne..." -------------------------------------------^
Linux-Default
Process completed with exit code 1.
Linux-Default
Exit code = 1
ServiceControlTransport: /_/src/ServiceControl.Transports.Tests/API/APIApprovals.cs#L14
System.Exception : Approval verification failed. - Approval File: APIApprovals.ServiceControlTransport.approved.txt (length=13710) - Received File: APIApprovals.ServiceControlTransport.received.txt (length=13813) Approved: ErrorQueue *** get; set; ***\n public int? MaxConcurrency *** get; set; ***\n Received: ErrorQueue *** get; set; ***\n public System.Collections.Generic.IReadOnlySet< ---------------------------------------------------^
Windows-Default
Process completed with exit code 1.
Windows-Default
Exit code = 1
ServiceControlTransport: /_/src/ServiceControl.Transports.Tests/API/APIApprovals.cs#L14
System.Exception : Approval verification failed. - Approval File: APIApprovals.ServiceControlTransport.approved.txt (length=13710) - Received File: APIApprovals.ServiceControlTransport.received.txt (length=13813) Approved: ErrorQueue *** get; set; ***\n public int? MaxConcurrency *** get; set; ***\n Received: ErrorQueue *** get; set; ***\n public System.Collections.Generic.IReadOnlySet< ---------------------------------------------------^
Windows-PrimaryRavenAcceptance
Process completed with exit code 1.
Windows-PrimaryRavenAcceptance
Exit code = 1
Should_publish_notification: /_/src/ServiceControl.AcceptanceTests/Monitoring/ExternalIntegration/When_a_custom_check_fails.cs#L62
Assert.That(enclosedType, Is.EqualTo("ServiceControl.Contracts.CustomCheckFailed, ServiceControl.Contracts")) Expected string length 68 but was 135. Strings differ at index 68. Expected: "...led, ServiceControl.Contracts" But was: "...led, ServiceControl.Contracts, Version=5.0.0.0, Culture=ne..." -------------------------------------------^
container-test / asq
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Particular/setup-azurestorage-action@v2.0.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/
Linux-PostgreSQL
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Particular/setup-postgres-action@v1.1.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/
Linux-AzureStorageQueues
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Particular/setup-azurestorage-action@v2.0.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/
Windows-PostgreSQL
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Particular/setup-postgres-action@v1.1.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/
Linux-RabbitMQ
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Particular/setup-rabbitmq-action@v1.7.1. 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/
Windows-AzureStorageQueues
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Particular/setup-azurestorage-action@v2.0.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/
Windows-RabbitMQ
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Particular/setup-rabbitmq-action@v1.7.1. 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/
windows-installers / build
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-MSMQ
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-PostgreSQL
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-PrimaryRavenPersistence
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-AzureStorageQueues
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-SqlServer
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-SQS
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-AzureServiceBus
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-Default
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-PrimaryRavenAcceptance
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows-RabbitMQ
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
Linux-assets Expired
328 MB
sha256:28f2323d9223f9c4f7a8560e0cd044b436cfaf18b1a2a2b929941759bfc3ece8
Particular~ServiceControl~EFWZML.dockerbuild
88.1 KB
sha256:4b6e97dbf368381cbfa2bcd6f4bef39f54a489c87672ed1d4d25ff3fce43defe
Particular~ServiceControl~JDNGJT.dockerbuild
89.1 KB
sha256:be0fe9274cb33695534025e0553187008f1b9edba7fc967c77482529110cd948
Particular~ServiceControl~QSXHMK.dockerbuild
86 KB
sha256:1d834fda8251d434ec64b13c903ca23f48d3a16e563bf691a5dddca2cb1facc4
Windows-assets Expired
322 MB
sha256:e38f3118f5f68e7b62c6a87456ca9212cf3e05dcbc58dfff4d6490b4ec580d84
assets Expired
455 MB
sha256:b221550954b658c70573cd560d611396dd09ddbec2ebd66cd29a1fc739d94b4d
nugets Expired
26.4 MB
sha256:1deb1cbd9a6149ada6dfd2823282faade91b21b4a2eac89ffe65fde8459689a7
zips Expired
189 MB
sha256:f9ea8e037c9f544a76fa969b0f05aab65d7ccfb8fa59e76f1e79d4defb98e9f4