Make WordPress Core


Ignore:
Timestamp:
08/01/2025 12:42:18 PM (7 months ago)
Author:
desrosj
Message:

Build/Test Tools: Spawn fewer jobs in GitHub Actions on forks.

The GitHub Actions workflows currently limit when jobs run for forks by short-circuiting any that are triggered by push events when not running within the wordpress-develop repository.

Because the large majority of forks are not created under organizations, they will be subject to the individual account limit of 20 concurrent jobs (40 for pro accounts) at any given time instead of the 500 concurrent job limit that applies to the WordPress organization. This means that a single pull request back to a fork can take several hours to complete the workflow jobs that are spawned.

This revises the conditional statements to further limit the number of jobs that spawn within a fork while still allowing the full test matrices for forks within the WordPress organization and pull requests back to wordpress-develop.

These adjustments result in a maximum of 53 jobs when all workflows configured to run within forks are triggered. Of these, ~66% will run in less than 3 minutes, and ~55% will run in less than 1 minute.

Props jorbin, johnbillion.
Fixes #63752.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/.github/workflows/local-docker-environment.yml

    r60532 r60534  
    7474      contents: read
    7575    secrets: inherit
    76     if: ${{ github.repository == 'WordPress/wordpress-develop' || ( github.event_name == 'pull_request' && github.actor != 'dependabot[bot]' ) }}
     76    if: ${{ github.repository == 'WordPress/wordpress-develop' }}
    7777    with:
    7878      wp-version: ${{ github.event_name == 'pull_request' && github.base_ref || github.ref_name }}
Note: See TracChangeset for help on using the changeset viewer.