[GHC] #15937: CI strategy for Gitlab

[GHC]

#15937: CI strategy for Gitlab
-------------------------------------+-------------------------------------
        Reporter:  alpmestan         |                Owner:  alpmestan
            Type:  task              |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Continuous        |              Version:
  Integration                        |
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by goldfire):

 Thanks for the careful thought here.

 If I push to a fork and want CI on my fork, I don't mind a few extra
 clicks, etc., to get CI working. (E.g., I might need to make an account
 somewhere and link it somehow.) Would requiring contributors to take a few
 steps like this unlock a better approach?

 (Note: I really don't have any idea of what I'm talking about here, and
 it's not worth your time to offer a long explanation of why such a thing
 isn't possible. If this comment is not helpful, just say "no" and invest
 your time in building the solution you think is best.)

-- 
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/15937#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler