Fix issues with Gitea using workers
This commit is contained in:
@@ -86,18 +86,25 @@ jobs:
|
||||
|
||||
- name: Test
|
||||
env:
|
||||
# Defaults match docker-compose.yml published ports; fixtures fall back to these anyway.
|
||||
# act_runner runs in its own container; Compose publishes ports on the VM.
|
||||
# host.docker.internal reaches those published ports (requires extra_hosts
|
||||
# host-gateway on the runner). RabbitMQ guest remote access is enabled in
|
||||
# infra/rabbitmq/rabbitmq.conf for this topology.
|
||||
ConnectionStrings__DefaultConnection: "Host=host.docker.internal;Port=5436;Database=vigilcare_test;Username=postgres;Password=password"
|
||||
ConnectionStrings__GatewayDb: "Host=host.docker.internal;Port=5437;Database=vigilcare_ward_test;Username=postgres;Password=password"
|
||||
Redis__ConnectionString: "host.docker.internal:6382,defaultDatabase=1,allowAdmin=true"
|
||||
Gateway__Redis__ConnectionString: "host.docker.internal:6383,defaultDatabase=2,allowAdmin=true"
|
||||
RabbitMq__Host: "host.docker.internal"
|
||||
RabbitMq__Port: "5674"
|
||||
Gateway__RabbitMq__Host: "host.docker.internal"
|
||||
Gateway__RabbitMq__Port: "5675"
|
||||
Kafka__BootstrapServers: "host.docker.internal:9092"
|
||||
Kafka__ReplicationFactor: "1"
|
||||
Kafka__SecurityProtocol: "Plaintext"
|
||||
Elasticsearch__Uri: "http://host.docker.internal:9200"
|
||||
Minio__Endpoint: "host.docker.internal:9005"
|
||||
Minio__UseSSL: "false"
|
||||
ASPNETCORE_ENVIRONMENT: "Testing"
|
||||
run: |
|
||||
dotnet test VigilCareClinical.sln -c Release --no-build \
|
||||
--logger "trx;LogFileName=test-results.trx" \
|
||||
|
||||
Reference in New Issue
Block a user