[wp-meta] [Making WordPress.org] #5275: Smarter nightly refreshing

[Making WordPress.org]

#5275: Smarter nightly refreshing
-------------------------+-------------------------
 Reporter:  desrosj      |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  General      |   Keywords:  2nd-opinion
-------------------------+-------------------------
 It's not uncommon for external repositories to configure the PHPUnit test
 suite for WordPress to be copied directly from `trunk`.

 For example, the [https://github.com/wp-cli/scaffold-
 command/blob/master/templates/install-wp-tests.sh install script used in
 the WP-CLI scaffold command] follows this approach. If `trunk` or
 `nightly` is specified as the version, the test suite is copied using `svn
 co` directly from `trunk`. However, when downloading WordPress' nightly
 version, the `https://wordpress.org/nightly-builds/wordpress-latest.zip`
 package is used instead (assuming for performance reasons).

 This causes any test setup configured using the WP-CLI scaffold command to
 fail until the nightly is refreshed any time files are moved or added in
 Core that tests rely on.

 There were two situations where this came up this week:
 - PHPMailer update, which moved the
 [https://core.trac.wordpress.org/changeset/47902 libraries files into a
 new directory].
 - The [https://core.trac.wordpress.org/changeset/48072 XML Sitemap feature
 plugin being merged].

 Manually refreshing the nightly fixed all issues reported by external
 projects.

 There is an [https://github.com/wp-cli/scaffold-command/issues/267
 upstream issue] for this on the WP-CLI Scaffold repo, but that would only
 apply to projects going forward, or ones that update their install script.

 Is it possible to set up "smarter" nightly refreshing where the nightly
 package gets rebuilt automatically if files are added, moved, or the
 `tests/phpunit/includes` directory is modified? That would ensure issues
 are failures in external projects have the potential to fail for a much
 smaller window than files are shuffled around or added.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5275>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org