[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 amontero):

 Here's my feedback from what I've understood from http://about.travis-
 ci.org/blog/announcing-pull-request-support .

 I'm a PHP programmer and sysadmin. So, no code contributions to Tahoe-LAFS
 by now, just docs. However, I think that automating tests as described
 above would help to lower the code contributor entry barrier and ease
 reviewer's work.

 Imagine I finally find the time to learn Python and want to get my feet
 wet with Tahoe-LAFS. I fork on GH and start hacking.
 1. As I'm learning, it may take some time. New tests may be written
 meanwhile and since CI happens against current upstream, those new tests
 may trigger new errors to me.
 2. Reviewers won't even know about my attempts, since CI would happen in
 my branch even before submitting my PR. Less noise for them.
 3. Reviewers found new tests worth automating. Someone (even the wanna be
 contributor) writes them, improving overall QA. All this in a separate/own
 branch. Less noise again (now and in the future).

 I'm not too familiar with Travis. I come from Drupal and each core
 submitted patch is automatically testbotted at submission and it helps a
 lot when you are in the learning phase of contribution (think on all those
 GSoCcers and newbies out there).
 Setting a local Travis may be an added difficulty for newcomers. I find
 Tahoe's code intimidating enough for a newbie to add the CI to the
 picture.

 I'm assuming that the local tests described in https://tahoe-lafs.org/trac
 /tahoe-lafs/wiki/AdvancedInstall#point8 can be run by Travis-CI
 automatically. Is this possible?

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