[tahoe-lafs-trac-stream] [tahoe-lafs] #2052: Automate testing of merge requests to streamline review.

[tahoe-lafs]

#2052: Automate testing of merge requests to streamline review.
--------------------------+-----------------------------------------
     Reporter:  nejucomo  |      Owner:  daira
         Type:  defect    |     Status:  new
     Priority:  normal    |  Milestone:  undecided
    Component:  unknown   |    Version:  1.10.0
   Resolution:            |   Keywords:  dev-infrastructure buildbot
Launchpad Bug:            |
--------------------------+-----------------------------------------

Comment (by markberger):

 For travis, the developer doesn't specify the commit to test. Instead,
 travis just selects the latest commit in the series. Here is an example of
 what travis looks like with multiple commits: https://github.com/rspec
 /rspec-core/pull/1027

 Another potential solution to this ticket would be to write a Github bot.
 For example, someone opens a pull request and a developer reviews it. If
 the developer thinks everything looks good they would comment on the pull
 request `@tahoe-bot: test`. This would trigger buildbot to fetch the the
 pull request and run the tests. The bot then comments on the pull request
 accordingly. To solve the security issue, only allow members of the Tahoe-
 LAFS organization to trigger forced builds.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2052#comment:3>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage