[tahoe-lafs-trac-stream] [tahoe-lafs] #2072: decide whether to enable Travis-CI for the main Tahoe-LAFS repo

[tahoe-lafs]

#2072: decide whether to enable Travis-CI for the main Tahoe-LAFS repo
-------------------------+-------------------------------------------------
     Reporter:  daira    |      Owner:  warner
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  dev-     |    Version:  1.10.0
  infrastructure         |   Keywords:  security travis github brians-
   Resolution:           |  opinion-needed
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by daira):

 Replying to [comment:10 warner]:
 > Is travis really capable of running our build and test suite? Its
 buildslaves are all donated by supporters, and impose a pretty strict
 timeout.

 The timeout is [https://github.com/travis-ci/travis-ci/issues/1362 50
 minutes, or 10 minutes with no output], which is fine for Tahoe-LAFS' test
 suite.

 Do you think the remaining permission issue is important enough to justify
 the separate daemon? It seems like quite a bit of work. Personally I don't
 mind that the `travis-tahoe` user can commit ''provided'' that it can only
 commit as itself, which I think is the case.

 If revoking the admin permission after setting the hook is okay, then
 please give `travis-tahoe` admin access to `tahoe-lafs/tahoe-lafs` (in a
 new Team so that you can change that permission independently).

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