On Thu, 2016-07-21 at 00:15 +0200, Ben Gamari wrote: > Ben Gamari <[email protected]> writes: > > > [ Unknown signature status ] > > > > Hello everyone, > > > > While picking up the pieces from a failed merge today I realized > > that we > > currently spend a fair bit of carbon footprint and CPU cycles > > making > > Travis test GHC yet the results of these tests aren't pushed > > anywhere. > > > > Would anyone object to having Travis push notifications of changes > > in > > red/green state to [email protected]? Perhaps this will allow > > some > > of us to react more quickly to regressions. > > > Actually Thomas points out that we indeed used to do this and yet > stopped because it meant that users would fork the repository, enable > Travis build on their fork, and then inadvertantly spam the list. So, > perhaps we shouldn't do this.
I think it could be controlled by an environment variable set in travis UI ( https://travis-ci.org/ghc/ghc/settings ). Repository fork will not clone the variables. Thanks, Yuras. > > - Ben > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
