[wp-trac] [WordPress Trac] #34694: Facilitate automated testing in context of pull requests and diffs

WordPress Trac noreply at wordpress.org
Wed Dec 9 22:00:39 UTC 2015


#34694: Facilitate automated testing in context of pull requests and diffs
------------------------------+------------------------
 Reporter:  westonruter       |       Owner:  jorbin
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  4.5
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------
Changes (by westonruter):

 * owner:   => jorbin
 * status:  new => reviewing


Comment:

 @jorbin The patch here is specifically for facilitating forks on GitHub to
 integrate their own extensions to how Travis CI runs, such as integrating
 with an external bot to upload the patches to Trac. The
 [https://github.com/xwp/wp-github-pull-request-travis-ci-trac-sync
 demonstrated extension] also add PHP_CodeSniffer and JSCS checks to the
 diff between `master` and the feature branch in the pull request. _But_
 the code required for this (the `class-git-patch-checker.php` and related
 scripts) can be put into Core `tools/`. When Travis runs inside the
 context of a pull request, it can do the coding standards checks on the
 diff between the feature branch and `master`. But, when Travis runs
 ''outside'' the context of a pull request, what we can do is use the
 latest stable release tag (e.g. `4.4.0`) as the start commit for the range
 of commits to check coding standards on. This will allow us to release-by-
 release enforcing coding standards via CI checks.

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


More information about the wp-trac mailing list