The OCaml Planet RSS

This post explores two more sustainable solutions to the crawler bots issue affecting opam-repo-ci

The same OCaml build matrix updates which where deployed in opam-repo-ci have now been applied to ocaml-ci.

Updates to opam-repo-ci which pull in the latest ocaml-version and ocaml-dockerfile releases trim the build matrix and add in the latest releases of Alpine and Ubuntu.

We’ve all been using Claude via the prompt, and some have even ventured into running claude --dangerously-skip-permissions in a nice sandbox like avsm/claude-ocaml-devcontainer.

We use OCluster to manage the build cluster for the CI services backing OCaml-CI and opam-repo-ci. However, it is a general-purpose tool and isn’t tied to being a build system; it can distribute any jobs across multiple worker machines.

Early in the upgrade program for Ubuntu 24.04, there were permission issues when extracting tar files. The workaround was to update to the latest dev version of Docker. However, this didn’t resolve all the issues on ARM64, so only one machine was updated and excluded from the base image builder work.

OCurrent has long wanted to access private repositories. You can achieve this by embedding a scoped PAT in the .git-credentials file, typically within the Docker container; however, this is untidy, to say the least! The approach presented works in cases where a GitHub app is used.

Would you like to build every package in opam in a single Dockerfile using BuildKit?

This morning, Anil proposed that having an opam-repository that didn’t have old versions of the packages that require patches to work with OxCaml would be good.

As @dra27 suggested, I first added support in ocurrent/ocaml-version. I went with the name flambda2, which matched the name in the opam package.