<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><blockquote type="cite" class=""><div class="">19.10.2017, 12:29 schrieb Ben Gamari <<a href="mailto:ben@well-typed.com" class="">ben@well-typed.com</a>>:</div><div class=""><div class="">Manuel M T Chakravarty <<a href="mailto:manuel.chakravarty@tweag.io" class="">manuel.chakravarty@tweag.io</a>> writes:<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">13.10.2017, 00:18 schrieb Ben Gamari <<a href="mailto:ben@well-typed.com" class="">ben@well-typed.com</a>>:<br class="">It's still quite unclear to me what a CircleCI/Appveyor solution will</blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class="">ultimately cost, but will almost certainly not be free. Assuming there<br class="">are users who are willing to foot that bill, this is of course fine.<br class="">However, it's quite contrary to the assumptions we have been working<br class="">with for much of this process.<br class=""></blockquote><br class="">Yes, you are right. That we have sponsors for the CI costs changes the<br class="">situation wrt to the previous planning. And it is precisely one of the<br class="">reasons why we founded the GHC DevOps group: to unlock new resources.<br class=""><br class="">I am sorry that this comes in the middle of the existing effort. I can<br class="">see how this is annoying. However, all the work on getting GHC’s build<br class="">in shape and the scripts to generate artefacts are all still needed.<br class=""></blockquote><br class="">Indeed the timing was slightly suboptimal but I'm nevertheless very glad<br class="">you brought this up. You have definitely helped me better understand the<br class="">trade-offs at play and I think at this point I can say that, despite the<br class="">costs, moving to CircleCI/Appveyor is the right decision.<br class=""></div></div></blockquote><div><br class=""></div>Ok, great. Thank you for pushing us to think through all the various issues.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">This is especially true in light of today's news that Rackspace will be<br class="">ending their open source support program at the end of this year, which<br class="">makes sustaining any self-hosted solution significantly harder<br class="">resource-wise.<br class=""></div></div></blockquote><div><br class=""></div>Oh, I didn’t know that. Will that affect <a href="http://haskell.org" class="">haskell.org</a> as well?</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">Let's figure out how to make this happen. This week is turning out to be<br class="">a bit busy for me, but perhaps this weekend or next week I'll see what<br class="">can be done to hook up Phabricator and try to get the build automation<br class="">in place for i386 and CentOS. However, if you have time do feel free to<br class="">start plugging away at this yourself in the meantime.<br class=""></div></div></blockquote><div><br class=""></div></div>Jonas spent some time on the macOS build on CircleCI.<div class=""><br class=""></div><div class="">It might be useful to make a list of all the things that need to be done and add it to the CI Trac page. Should we take a stab at that next week (when your schedule calms down a bit)?</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Manuel</div><div class=""><br class=""></div></body></html>