[ocaml-infra] Staging Build and Deployment of ocaml.org

[Ashish Agarwal]

Got it. Makes sense.


On Mon, Mar 17, 2014 at 10:47 AM, Anil Madhavapeddy <anil at recoil.org> wrote:

> On 17 Mar 2014, at 14:19, Ashish Agarwal <agarwal1975 at gmail.com> wrote:
>
> On Mon, Mar 17, 2014 at 7:49 AM, David Sheets <sheets at alum.mit.edu> wrote:
>
> Specifically, I'd like to see:
>>
>> 1. Generated assets and build logs publicly accessible
>> 2. Build environment specification (e.g. "this stock Ubuntu image").
>> 3. History
>>
>
> All of these could be obtained with a single server. Can you explain the
> benefits of splitting into a build server and static server. I'm just
> wondering why the extra work would be worth it.
>
>
> Because the set of people that need to build ocaml.org is higher than the
> set of deployment services we need to support.  Separating them would let
> us triage ocaml.org build failures (e.g. the obscure awk issue, or the
> sorts of problem that Michel or Jacques had as first time contributors),
> from errors in the deployment system (due to some Git infrastructure or
> whatever going down).
>
> We currently implicitly support quite a few build environments (e.g. MacOS
> X in addition to Ubuntu), so gradually adding more CI to ensure all this
> stays working means less work for us in the long term.  Note that this
> isn't specifically an ocaml.org issue -- any such CI could also help OPAM
> package testing expand out beyond Ubuntu x86_64.
>
> -anil
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/infrastructure/attachments/20140317/4cc11238/attachment.html>