mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-16 09:52:54 +00:00
92273b6d5e
## Problem Currently, we run the `pg_regress` tests only for PG16 However, PG17 is a part of Neon and should be tested as well ## Summary of changes Modified the workflow and added a patch for PG17 enabling the `pg_regress` tests. The problem with leftovers was solved by using branches.
26 lines
610 B
YAML
26 lines
610 B
YAML
self-hosted-runner:
|
|
labels:
|
|
- arm64
|
|
- large
|
|
- large-arm64
|
|
- small
|
|
- small-arm64
|
|
- us-east-2
|
|
config-variables:
|
|
- AZURE_DEV_CLIENT_ID
|
|
- AZURE_DEV_REGISTRY_NAME
|
|
- AZURE_DEV_SUBSCRIPTION_ID
|
|
- AZURE_PROD_CLIENT_ID
|
|
- AZURE_PROD_REGISTRY_NAME
|
|
- AZURE_PROD_SUBSCRIPTION_ID
|
|
- AZURE_TENANT_ID
|
|
- BENCHMARK_PROJECT_ID_PUB
|
|
- BENCHMARK_PROJECT_ID_SUB
|
|
- REMOTE_STORAGE_AZURE_CONTAINER
|
|
- REMOTE_STORAGE_AZURE_REGION
|
|
- SLACK_UPCOMING_RELEASE_CHANNEL_ID
|
|
- DEV_AWS_OIDC_ROLE_ARN
|
|
- BENCHMARK_INGEST_TARGET_PROJECTID
|
|
- PGREGRESS_PG16_PROJECT_ID
|
|
- PGREGRESS_PG17_PROJECT_ID
|