<div dir="ltr">Thanks for the great summary, Ben.<br><div><div class="gmail_extra"><br><div class="gmail_quote">On 5 March 2018 at 17:15, Ben Gamari <span dir="ltr"><<a href="mailto:ben@well-typed.com" target="_blank">ben@well-typed.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
The following things are rather lacking direction at the moment,<br>
<br>
a. Integration between Phabricator and Appveyor/CircleCI (#14506).<br></blockquote><div><br></div><div>What are our options here? I presume we'll have to write some custom integration?<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
b. Validation of each commit in a push as both Appveyor and CircleCI<br>
only build the push head (#14505). This is quite important as having<br>
a full commit history has been invaluable in identifying<br>
regressions. I will start pushing commits one-at-a-time until this<br>
is sorted out.<br>
<br>
c. Artifact preservation. I recommend that we push these to S3 or<br>
similar to avoid relying on Appveyor/CircleCI's (generally rather<br>
restrictive) artifact archival facilities.<br>
<br>
d. Hadrian builds seem to non-deterministically hang on CircleCI<br>
(#14600). I've never observed this locally and have had no luck<br>
reproducing via SSH on a CircleCI box, so it's unclear what to do<br>
about this.<br>
<br>
e. Support for building on non-Debian-based systems (e.g. Fedora),<br>
which is necessary if we want to produce our binary distributions<br>
via CI<br>
<br>
I suspect that after (b) is fixed we will find that the computational<br>
resources of our CircleCI account may be a bit lacking, but we can cross<br>
that bridge once we get there.<br></blockquote><div><br></div><div>I think the same will be true of (a).<br><br></div><div>Cheers<br></div><div>Simon<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cheers,<br>
<br>
- Ben<br>
<br>
<br>
[1] <a href="https://circleci.com/gh/ghc/ghc/tree/master" rel="noreferrer" target="_blank">https://circleci.com/gh/ghc/<wbr>ghc/tree/master</a><br>
[2] <a href="https://ci.appveyor.com/project/GHCAppveyor/ghc" rel="noreferrer" target="_blank">https://ci.appveyor.com/<wbr>project/GHCAppveyor/ghc</a><br>
[3] <a href="https://github.com/ghc/ghc/pull/104" rel="noreferrer" target="_blank">https://github.com/ghc/ghc/<wbr>pull/104</a><br>
[4] <a href="https://github.com/ghc/ghc/pull/106" rel="noreferrer" target="_blank">https://github.com/ghc/ghc/<wbr>pull/106</a><br>
<br>______________________________<wbr>_________________<br>
Ghc-devops-group mailing list<br>
<a href="mailto:Ghc-devops-group@haskell.org">Ghc-devops-group@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devops-group" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/ghc-<wbr>devops-group</a><br>
<br></blockquote></div><br></div></div></div>