<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="font-family: monospace; font-size: 15px;">[RESENT MESSAGE — see <a href="https://mail.haskell.org/pipermail/ghc-devops-group/2017-October/000004.html" class="">https://mail.haskell.org/pipermail/ghc-devops-group/2017-October/000004.html</a>]</div><div class=""><br class=""></div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">"Boespflug, Mathieu" <<a href="mailto:m@tweag.io" class="">m@tweag.io</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">Aw: [GHC DevOps Group] Phabricator -> GitHub?</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">10. Oktober 2017 um 08:10:39 GMT+11<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Simon Marlow <<a href="mailto:marlowsd@gmail.com" class="">marlowsd@gmail.com</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Cc: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Manuel M T Chakravarty <<a href="mailto:manuel.chakravarty@tweag.io" class="">manuel.chakravarty@tweag.io</a>>, <a href="mailto:ghc-devops-group@haskell.org" class="">ghc-devops-group@haskell.org</a><br class=""></span></div><br class=""><div class=""><div class="">Hi Simon,<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Secondly, the suggestion was only to use <a href="http://reviewable.io" class="">reviewable.io</a> for particularly<br class="">heavy PRs.<br class=""></blockquote><br class=""><br class="">I think that would be worse, because we have some PRs going through<br class="">different code review tools. On Phabricator I have a single dashboard that<br class="">shows me which PRs are needing my attention, I don't want to have to visit<br class="">two different tools to see that.<br class=""></blockquote></blockquote><br class="">I agree with you that not having all PR's in a single dashboard would<br class="">be very inconvenient. But note that even with <a href="http://reviewable.io" class="">reviewable.io</a> (which I<br class="">think really isn't very necessary at this point, but is at least an<br class="">option), you'd still have a single dashboard, that dashboard being the<br class="">GitHub PR dashboard you know currently.<br class=""><br class="">The essential difference is that <a href="http://reviewable.io" class="">reviewable.io</a> is not an alternate<br class="">tool. It's an opt-in thin layer on top of GitHub.<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><br class="">Thirdly, it still is much better than Phabricator on the new random tool<br class="">front because it requires no custom infrastructure and the PRs still go<br class="">through GitHub as usual.<br class=""></blockquote><br class=""><br class="">I do buy the custom infrastructure argument in general - setting up our<br class="">own CI has definitely taken a lot of Ben's time. I actually really liked<br class="">having Travis for my GHC fork on GitHub. That was when it used to work,<br class="">before our build exceeded what Travis would give us. So I guess that<br class="">illustrates two things: custom infrastructure is nice when it works, but<br class="">we're at the mercy of the suppliers.<br class=""></blockquote></blockquote><br class="">Just another note here: these kinds of limits have proven "soft" in<br class="">the past, in that the Travis CI folks have been willing to bump the<br class="">limits for a large project like GHC. I'd be surprised if they weren't<br class="">willing to bump these limits some more, especially for a highly<br class="">visible open source project like GHC. In any case, I've had very good<br class="">success setting up CI for Tweag I/O's GHC fork for linear types on top<br class="">of CircleCI, which has the option run on faster machines, and also has<br class="">less aggressive limits. I hear the Hadrian project still uses Travis<br class="">CI to good effect. In terms of effort vs quality, to setup something<br class="">that's a) uses only scalable resources, and b) is completely<br class="">reproducible by anyone, both these hosted CI options proved to have a<br class="">very good ratio indeed.<br class=""></div></div></blockquote><blockquote type="cite" class=""><div class="">Anfang der weitergeleiteten Nachricht:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Von: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">"Boespflug, Mathieu" <<a href="mailto:m@tweag.io" class="">m@tweag.io</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Betreff: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">Aw: [GHC DevOps Group] Phabricator -> GitHub?</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Datum: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">10. Oktober 2017 um 08:10:39 GMT+11<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">An: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Simon Marlow <<a href="mailto:marlowsd@gmail.com" class="">marlowsd@gmail.com</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Kopie: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Manuel M T Chakravarty <<a href="mailto:manuel.chakravarty@tweag.io" class="">manuel.chakravarty@tweag.io</a>>, <a href="mailto:ghc-devops-group@haskell.org" class="">ghc-devops-group@haskell.org</a><br class=""></span></div><br class=""><div class=""><div class="">Hi Simon,<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Secondly, the suggestion was only to use <a href="http://reviewable.io" class="">reviewable.io</a> for particularly<br class="">heavy PRs.<br class=""></blockquote><br class=""><br class="">I think that would be worse, because we have some PRs going through<br class="">different code review tools. On Phabricator I have a single dashboard that<br class="">shows me which PRs are needing my attention, I don't want to have to visit<br class="">two different tools to see that.<br class=""></blockquote></blockquote><br class="">I agree with you that not having all PR's in a single dashboard would<br class="">be very inconvenient. But note that even with <a href="http://reviewable.io" class="">reviewable.io</a> (which I<br class="">think really isn't very necessary at this point, but is at least an<br class="">option), you'd still have a single dashboard, that dashboard being the<br class="">GitHub PR dashboard you know currently.<br class=""><br class="">The essential difference is that <a href="http://reviewable.io" class="">reviewable.io</a> is not an alternate<br class="">tool. It's an opt-in thin layer on top of GitHub.<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><br class="">Thirdly, it still is much better than Phabricator on the new random tool<br class="">front because it requires no custom infrastructure and the PRs still go<br class="">through GitHub as usual.<br class=""></blockquote><br class=""><br class="">I do buy the custom infrastructure argument in general - setting up our<br class="">own CI has definitely taken a lot of Ben's time. I actually really liked<br class="">having Travis for my GHC fork on GitHub. That was when it used to work,<br class="">before our build exceeded what Travis would give us. So I guess that<br class="">illustrates two things: custom infrastructure is nice when it works, but<br class="">we're at the mercy of the suppliers.<br class=""></blockquote></blockquote><br class="">Just another note here: these kinds of limits have proven "soft" in<br class="">the past, in that the Travis CI folks have been willing to bump the<br class="">limits for a large project like GHC. I'd be surprised if they weren't<br class="">willing to bump these limits some more, especially for a highly<br class="">visible open source project like GHC. In any case, I've had very good<br class="">success setting up CI for Tweag I/O's GHC fork for linear types on top<br class="">of CircleCI, which has the option run on faster machines, and also has<br class="">less aggressive limits. I hear the Hadrian project still uses Travis<br class="">CI to good effect. In terms of effort vs quality, to setup something<br class="">that's a) uses only scalable resources, and b) is completely<br class="">reproducible by anyone, both these hosted CI options proved to have a<br class="">very good ratio indeed.<br class=""></div></div></blockquote><blockquote type="cite" class=""><div class="">Anfang der weitergeleiteten Nachricht:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Von: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">"Boespflug, Mathieu" <<a href="mailto:m@tweag.io" class="">m@tweag.io</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Betreff: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">Aw: [GHC DevOps Group] Phabricator -> GitHub?</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Datum: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">10. Oktober 2017 um 08:10:39 GMT+11<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">An: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Simon Marlow <<a href="mailto:marlowsd@gmail.com" class="">marlowsd@gmail.com</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Kopie: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:ghc-devops-group@haskell.org" class="">ghc-devops-group@haskell.org</a><br class=""></span></div><br class=""><div class=""><div class="">Hi Simon,<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Secondly, the suggestion was only to use <a href="http://reviewable.io" class="">reviewable.io</a> for particularly<br class="">heavy PRs.<br class=""></blockquote><br class=""><br class="">I think that would be worse, because we have some PRs going through<br class="">different code review tools. On Phabricator I have a single dashboard that<br class="">shows me which PRs are needing my attention, I don't want to have to visit<br class="">two different tools to see that.<br class=""></blockquote></blockquote><br class="">I agree with you that not having all PR's in a single dashboard would<br class="">be very inconvenient. But note that even with <a href="http://reviewable.io" class="">reviewable.io</a> (which I<br class="">think really isn't very necessary at this point, but is at least an<br class="">option), you'd still have a single dashboard, that dashboard being the<br class="">GitHub PR dashboard you know currently.<br class=""><br class="">The essential difference is that <a href="http://reviewable.io" class="">reviewable.io</a> is not an alternate<br class="">tool. It's an opt-in thin layer on top of GitHub.<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><br class="">Thirdly, it still is much better than Phabricator on the new random tool<br class="">front because it requires no custom infrastructure and the PRs still go<br class="">through GitHub as usual.<br class=""></blockquote><br class=""><br class="">I do buy the custom infrastructure argument in general - setting up our<br class="">own CI has definitely taken a lot of Ben's time. I actually really liked<br class="">having Travis for my GHC fork on GitHub. That was when it used to work,<br class="">before our build exceeded what Travis would give us. So I guess that<br class="">illustrates two things: custom infrastructure is nice when it works, but<br class="">we're at the mercy of the suppliers.<br class=""></blockquote></blockquote><br class="">Just another note here: these kinds of limits have proven "soft" in<br class="">the past, in that the Travis CI folks have been willing to bump the<br class="">limits for a large project like GHC. I'd be surprised if they weren't<br class="">willing to bump these limits some more, especially for a highly<br class="">visible open source project like GHC. In any case, I've had very good<br class="">success setting up CI for Tweag I/O's GHC fork for linear types on top<br class="">of CircleCI, which has the option run on faster machines, and also has<br class="">less aggressive limits. I hear the Hadrian project still uses Travis<br class="">CI to good effect. In terms of effort vs quality, to setup something<br class="">that's a) uses only scalable resources, and b) is completely<br class="">reproducible by anyone, both these hosted CI options proved to have a<br class="">very good ratio indeed.<br class="">_______________________________________________<br class="">Ghc-devops-group mailing list<br class=""><a href="mailto:Ghc-devops-group@haskell.org" class="">Ghc-devops-group@haskell.org</a><br class="">https://haskell.org/cgi-bin/mailman/listinfo/ghc-devops-group<br class=""></div></div></blockquote></div><br class=""></body></html>