Opened 10 months ago
Last modified 10 months ago
#60370 new enhancement
Test Tools: Clarifying reusable workflows in Github CI
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | minor | Version: | |
| Component: | Build/Test Tools | Keywords: | |
| Focuses: | Cc: |
Description
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).