[GHC] #13716: Move CI to Jenkins
Alexander Kjeldaas
alexander.kjeldaas at gmail.com
Thu Sep 7 07:24:34 UTC 2017
I find that using gitlab with a docker swarm is a good compromise.
Then gitlab runs all the infrastructure for the UI part, access control ++,
and all you have to do is to run the gitlab-runner docker image and
register it in gitlab.
This also brings other options such as having one run from scratch and
other "quick" runs where a half-built docker image is updated. I use
docker hub for syncing images between the registered docker runners.
Alexander
On Thu, Sep 7, 2017 at 4:13 AM, davean <davean at xkcd.com> wrote:
> Thats actually how this project started.
>
> On Wed, Sep 6, 2017 at 7:05 PM, GHC <ghc-devs at haskell.org> wrote:
>
>> #13716: Move CI to Jenkins
>> -------------------------------------+----------------------
>> ---------------
>> Reporter: bgamari | Owner: (none)
>> Type: task | Status: new
>> Priority: normal | Milestone:
>> Component: None | Version: 8.0.1
>> Resolution: | Keywords:
>> Operating System: Unknown/Multiple | Architecture:
>> | Unknown/Multiple
>> Type of failure: None/Unknown | Test Case:
>> Blocked By: 13897 | Blocking:
>> Related Tickets: #11958 | Differential Rev(s):
>> Wiki Page: |
>> -------------------------------------+----------------------
>> ---------------
>>
>> Comment (by refold):
>>
>> Is there any chance Cabal/cabal-install could piggyback on this effort?
>> We've outgrown free services like Travis and AppVeyor and could use
>> support for additional platforms (OpenBSD and maybe ARM) too.
>>
>> --
>> Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/13716#comment:6>
>> GHC <http://www.haskell.org/ghc/>
>> The Glasgow Haskell Compiler
>>
>
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20170907/a3f1d12a/attachment.html>
More information about the ghc-devs
mailing list