Hi Fabrice, Thanks for releasing this; it looks very useful! The build bot looks like it could also benefit from the container infrastructure, since that takes care of depexts for a number of distributions.
Before I look further at this, I just wanted to confirm that the licensing of the buildbot is intended to be fully AGPLv3. It looks like there's a fork of opamLib here: https://github.com/OCamlPro/opam-builder/tree/master/libs/copam <https://github.com/OCamlPro/opam-builder/tree/master/libs/copam> renamed under the copam namespace. regards, Anil > On 21 Mar 2016, at 12:43, Fabrice Le Fessant <fabrice.le_fess...@inria.fr> > wrote: > > Hi, > > In the last weeks, I have been working on a bot that monitors the > opam-repository and displays issues when linting and building the packages. > > Currently, the bot runs on a 4-core server with Debian 8, and prints > results for 3.12.1, 4.00.1, 4.01.0, 4.02.3 and 4.03.0+beta1: > > http://opam.ocamlpro.com/builder/html/report-last.html > <http://opam.ocamlpro.com/builder/html/report-last.html> > > It tries to keep up with the opam-repository, in a best effort way. > Compiling the full repository on one OCaml version can take one or two days, > but next compilations are incremental (only impacted packages are recompiled, > and binary archives are used to re-use previous compilations), so a report > for every commit should be available after only a few minutes/hours, > depending on the number of packages that need to be recompiled. > > The sources are available here, if you want to start it on a different > hardware/OS: > > https://github.com/OCamlPro/opam-builder > <https://github.com/OCamlPro/opam-builder> > > Feedback and PRs are welcome ! > --Fabrice > > _______________________________________________ > opam-devel mailing list > opam-devel@lists.ocaml.org > http://lists.ocaml.org/listinfo/opam-devel
_______________________________________________ opam-devel mailing list opam-devel@lists.ocaml.org http://lists.ocaml.org/listinfo/opam-devel
