[GHC DevOps Group] FreeBSD in Tier 1

[Boespflug, Mathieu]

Hi Ben,

great! The below message contains a good partial spec for what
behaviour we want from the CI system. To the point of my earlier
email, Manuel, Ben and Jonas - could you guys flesh out the
requirements we're shooting for in a wiki page?

Also, IMHO there are two stages to this: even just getting ./validate
to run on all Tier 1 (sans FreeBSD, candidate for demotion to Tier 2)
reliably and without suffering outages would be a useful addition to
today's arsenal. Then after that we can automate pushing release
artifacts to a durable location.

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


On 10 October 2017 at 03:38, Ben Gamari <ben at well-typed.com> wrote:
> Manuel M T Chakravarty <manuel.chakravarty at tweag.io> writes:
>
>> Yes, and we have got options for that, such as cross-compiling and
>> using QEMU. We will cross that bridge when we get to it.
>>
>> For now, please let us focus on our immediate goal of automatically
>> producing build artefacts to streamline the release process and for
>> providing reliable CI for the core platforms.
>>
>> Given the CircleCI config Mathieu already contributed, what is missing
>> to create the release artefacts on CircleCI?
>>
> Building release artifacts entails the following:
>
>  * Produce and archive a source distribution
>
>  * For each platform:
>
>     * Build a build in a release configuration from this source
>       distribution (not a checkout, to ensure that our packaging logic
>       is correct)
>
>     * Produce a binary distribution from this build
>
>     * Run test_bindist on the build
>
>     * Ideally also run the testsuite on this build
>
>     * Archive all of these artifacts
>
>  * Produce and archive a documentation tree
>
> You will find that these are the steps that my own release tooling
> performs [1].
>
> Cheers,
>
> - Ben
>
>
> [1] https://github.com/bgamari/ghc-utils/blob/master/rel-eng/bin-release.sh
>
>
> _______________________________________________
> Ghc-devops-group mailing list
> Ghc-devops-group at haskell.org
> https://haskell.org/cgi-bin/mailman/listinfo/ghc-devops-group
>