[GHC DevOps Group] Continuous integration effort status

[Boespflug, Mathieu]

Hi Ben,

good summary of the current directions the Group is pursuing.

>  * For the next day or two I am rather tied up with other things, but
>    after this I will have some time to look at the boxes that Greg has
>    brought up and see what it will take to bring up Appveyor. If someone
>    else would like to pick this up then do let me know.

Mark Karpov has started work on this today, using Tweag I/O's Premium
subscription for Appveyor until a subscription can be sorted out for
the ghc org.

Best,
--
Mathieu Boespflug
Founder at http://tweag.io.


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