[wp-trac] [WordPress Trac] #60370: Test Tools: Clarifying reusable workflows in Github CI
WordPress Trac
noreply at wordpress.org
Mon Jan 29 12:59:58 UTC 2024
#60370: Test Tools: Clarifying reusable workflows in Github CI
------------------------------+-----------------------------
Reporter: youknowriad | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Build/Test Tools | Version:
Severity: minor | Keywords:
Focuses: |
------------------------------+-----------------------------
While working on https://github.com/WordPress/wordpress-develop/pull/5922
we had to increase the timeout limit for one of the reusable workflows of
the repository: phpunit-tests-run.yml
The problem is that the update were not being taken into consideration in
the PR because we explicitly refer to the "trunk" version of that workflow
in `phpunit-tests.yml`
Github does offer a way to use relative links to other workflows from the
same repository (instead of URLs), ti would have solved the issue there
but it comes with a set of tradeoffs that need to be considered.
For example, updating Node.JS version in the reusable workflow would need
to be done for all the previous branches that WP still supports while
forcing the use of the "trunk" workflow means we can update in a single
place.
The initial discussion about this happened on the following Slack Thread
https://wordpress.slack.com/archives/C02RQBWTW/p1706523051675219
I'm opening this ticket so we can track this discussion and potentially
address it (or not).
--
Ticket URL: <https://core.trac.wordpress.org/ticket/60370>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list