name: jpa-nightly

# The suites that are too slow, too Docker-heavy, or too machine-dependent for a PR, and the middle
# of the PostgreSQL matrix.
#
# The failure-injection lane is the one that matters most and is easiest to lose: it is the only
# place the commit-ambiguity scenarios run, and they are the only evidence that a lost commit
# acknowledgement produces completion-unknown rather than a retry.

on:
  workflow_dispatch:
  schedule:
    # 02:30 UTC daily.
    - cron: '30 2 * * *'

permissions:
  contents: read

concurrency:
  group: ${{ github.workflow }}
  cancel-in-progress: false

jobs:
  jpa-full-matrix:
    runs-on: ubuntu-latest
    timeout-minutes: 60
    strategy:
      fail-fast: false
      matrix:
        postgresql: ["16", "17", "18"]
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
      - uses: ./.github/actions/setup-gradle-java
      - name: Certify the platform against PostgreSQL ${{ matrix.postgresql }}
        working-directory: src
        run: >-
          ./gradlew
          :adapter:outbound:persistence-jpa:jpaPlatformContractTest
          -Pjpa.matrix.versions=${{ matrix.postgresql }}
          --no-daemon
          --stacktrace

  jpa-failure-injection:
    runs-on: ubuntu-latest
    timeout-minutes: 45
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
      - uses: ./.github/actions/setup-gradle-java
      - name: Reproduce deadlock, serialization, and commit-ambiguity scenarios
        working-directory: src
        run: >-
          ./gradlew
          :adapter:outbound:persistence-jpa:jpaPlatformFailureTest
          --no-daemon
          --stacktrace

  jpa-query-plan-and-security:
    runs-on: ubuntu-latest
    timeout-minutes: 45
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
      - uses: ./.github/actions/setup-gradle-java
      - name: Run the query plan and database security suites
        working-directory: src
        run: >-
          ./gradlew
          :adapter:outbound:persistence-jpa:jpaPlatformQueryPlanTest
          :adapter:outbound:persistence-jpa:jpaPlatformSecurityTest
          --no-daemon
          --stacktrace

  jpa-pool-pressure:
    runs-on: ubuntu-latest
    timeout-minutes: 45
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
      - uses: ./.github/actions/setup-gradle-java
      - name: Verify pool saturation and REQUIRES_NEW connection behaviour
        working-directory: src
        # A behaviour contract, not a measurement. This step used to switch assertions off with an
        # explicit property and call the result a certification, so the only threshold it ever
        # asserted was that thresholds were not being asserted. What
        # it checks now — that REQUIRES_NEW needs two connections per concurrent thread, that a
        # saturated pool reports its pending count, that a caller waits rather than proceeding
        # without a connection — is true on any runner, so there is nothing to switch off.
        run: >-
          ./gradlew
          :adapter:outbound:persistence-jpa:jpaPlatformPoolContractTest
          --no-daemon
          --stacktrace