[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:  closed
     Priority:  normal           |  Milestone:  soon (release n/a)
    Component:  dev-             |    Version:  1.10.0
  infrastructure                 |
   Resolution:  fixed            |   Keywords:  dev-infrastructure buildbot
Launchpad Bug:                   |
---------------------------------+-----------------------------------------
Changes (by warner):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:  undecided => soon (release n/a)


Comment:

 I'm ok with relying on travis and github pull-requests for this. These
 days, the workflow is excellent, for both contributors and committers. The
 pull-request has little status badges that get updated when travis reports
 the status of the test build.

 Buildbot can stick to testing things that actually land on master. We get
 slightly better test coverage from buildbot (more than just linux), but I
 don't think it's worth the effort to try and provide that for pre-commit
 branches.

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