caml-list - the Caml user's mailing list
 help / Atom feed
From: Anil Madhavapeddy <>
To: Helmut Brandl <>
Cc: caml users <>
Subject: Re: [Caml-list] Opam packages and CI
Date: Tue, 9 Apr 2019 22:36:38 +0100
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]

On 9 Apr 2019, at 19:14, Helmut Brandl <> wrote:
> Hello list,
> I would like to run some continuous integration like travis ci on my opam package. Unfortunately ocaml is not supported directly by travis. But I have found the GitHub repository ocaml/ocaml-ci-scripts and some instructions on how to use it.

Dear Helmut,

> My questions:
> - Is this a stable form on how to use travis with ocaml?
> - Are there experiences and are they good?

Last I checked, there were over 400 repositories on GitHub using ocaml-ci-scripts.  It's pretty stable.

> - Why has this solution been chosen instead of integrating ocaml support directly into travis?

Why do you need direct integration with Travis?  The use of the Docker support has made the necessity for that essentially obsolete.

See, for example: <>

in cohttp, which uses Travis and Docker to test the libraries on a variety of Linux distributions.

> - Isn’t the solution an overkill, because it requires a complete opam and ocaml installation on the travis machines in order to test an opam package? Isn’t there the risk that travis might block this form of usage in the future?
> - Is there a better method to use CI with ocaml?

This solution is pretty good for most people. I'd encourage you to give it a try, and to contribute back any improvements or feature requests you might have after trying it out for a while.


[-- Attachment #2: Type: text/html, Size: 2754 bytes --]

  parent reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 18:14 Helmut Brandl
2019-04-09 18:49 ` Simon Cruanes
2019-04-09 18:54   ` Daniil Baturin
2019-04-09 21:36 ` Anil Madhavapeddy [this message]
2019-04-10 14:57   ` Helmut Brandl
2019-04-10 14:20 ` Louis Roché

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror

AGPL code for this site: git clone public-inbox