[wp-trac] [WordPress Trac] #59632: Test building Gutenberg plugin in GitHub Actions

[WordPress Trac]

#59632: Test building Gutenberg plugin in GitHub Actions
------------------------------+-----------------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Future Release
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+-----------------------------

Comment (by desrosj):

 I've started exploring adding some logic to test the Gutenberg plugin's
 build process in the context of a `wordpress-develop` checkout.

 For testing purposes, I reintroduced the failure caused by `grunt-contrib-
 qunit` to [https://github.com/WordPress/wordpress-
 develop/actions/runs/6537985303/job/17752977824#step:9:90 confirm the
 issue is caught in these tests].

 [https://github.com/WordPress/wordpress-develop/actions/runs/6538246913
 Here's a run after re-applying the fix].

 However, I was unable to reproduce the issue described in #58671. It's
 possible that issue has been resolved since the ticket was created,
 though.

 The attached PR also renames the `Test npm` workflow to be more generic.
 While we are testing that npm dependencies install correctly, what is
 actually being tested is that the build process is successful. If this is
 the road we choose to go down, the changes will either need to be
 backported, or the `Testing old branches` workflow will need to be updated
 to account for the workflow being called two different things in different
 branches once the 6.4 branch is created.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/59632#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform