[GHC DevOps Group] The future of Phabricator

[Ben Gamari]

Carter Schonwald <carter.schonwald at gmail.com> writes:

> For what it’s worth, I’ve never found phab / arc to be the bottle neck /
> actual time consuming piece of doing anything for ghc
>
> It’s defintely the nicest code review substrate I’ve engaged with
>
> One question I have : how does the llvm org manage / handle their
> phabricator instance and or ci substrate. Maybe they have wisdom that can
> help ?
>
LLVM uses Jenkins primarily for CI; it is not integrated with their
Phabricator instance.

Cheers,

- Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20181101/fd52e2c9/attachment.sig>