Thomas Leonard

If they're building the same thing on the same machine then it will just do one build and stream the same logs to both clients (for that build step).

What are we trying to test here? I see a couple of possibilities: 1. That a package's install/uninstall scripts work with a non-opam ocaml. That seems reasonable for opam-repo-ci, but...

Note that OCurrent's built-in history only works for builds with the same (primary) key. For example, the history of an ocaml-ci analyse job only shows builds for a single commit...

Yes, probably is quite a big job. As well as allowing customisation of the UI, it also needs the code to record the history (e.g. something that combines https://github.com/ocurrent/ocaml-ci/blob/master/lib/index.ml and...

Yes, but we do want it to use the cluster fully when the cluster isn't busy. Having 500 jobs at once is fine, as long as nothing else needs to...

Now that https://github.com/ocurrent/ocluster/pull/88 this PR shouldn't be needed.

Worth a try. Though I'm not sure where all the memory is actually going. opam-repo-ci has [memtrace](https://github.com/janestreet/memtrace) support compiled in, so it might be an idea to turn that on...

> if a dependency of (a) is updated, deployment thereof will only be done by a commit to mirage-www (AFAIU) The mirage-www build is controlled by the Dockerfile in the...

The log display is too narrow (for GitHub projects). It wastes most of the screen with borders, forcing you to scroll horizontally to read longer lines (it's fine for GitLab...

I would expect so, but with OBuilder rather than Docker now. Some kind of "dont-cache-result" flag there might be useful. Might save a fair bit of disk space too!