[Caml-list] Opam packages and CI

[Caml-list] Opam packages and CI

[Helmut Brandl]

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.

My questions:

- Is this a stable form on how to use travis with ocaml?

- Are there experiences and are they good?

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

- 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?

Thanks
Helmut

Re: [Caml-list] Opam packages and CI

[Simon Cruanes]

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

I've had good experiences with travis recently, using the docker script
(an example here:
https://github.com/c-cube/iter/blob/master/.travis.yml).

if your package is opam 2-friendly it's just a matter of a local pin
and a few switches. there are other options (variables, really) to
install extra deps or deal with optional deps.

It's not particularly overkill since it just starts with a docker image
with pre-installed opam switches.

-- 
Simon Cruanes

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [Caml-list] Opam packages and CI

[Daniil Baturin]

Apparently all it takes to add a "proper" Travis integration is three
people and some Ruby code.

https://docs.travis-ci.com/user/languages/community-supported-languages/#adding-a-new-language
https://github.com/travis-ci/travis-build/blob/master/spec/build/script/haskell_spec.rb

I don't have a Ruby experience myself though so I can hardly volunteer.

On 4/10/19 1:49 AM, Simon Cruanes wrote:
> I've had good experiences with travis recently, using the docker script > (an example here: >
https://github.com/c-cube/iter/blob/master/.travis.yml). > > if your
package is opam 2-friendly it's just a matter of a local pin > and a few
switches. there are other options (variables, really) to > install extra
deps or deal with optional deps. > > It's not particularly overkill
since it just starts with a docker image > with pre-installed opam
switches. >

Re: [Caml-list] Opam packages and CI

[Anil Madhavapeddy]

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

On 9 Apr 2019, at 19:14, Helmut Brandl <helmut.brandl@gmx.net> 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:
https://github.com/mirage/ocaml-cohttp/blob/master/.travis.yml <https://github.com/mirage/ocaml-cohttp/blob/master/.travis.yml>

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.

regards,
Anil

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

Re: [Caml-list] Opam packages and CI

[Helmut Brandl]

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

Thanks for all the hints. Some experiences:

I have used the .travis.yaml file from the repo ocaml/ocaml-ci-scripts, reduced the build matrix to a minimum (only 4.07) and it worked out of the box. However to took approx 8 min for linux and 12 min for osx.

Therefore I have changed in the travis file ‘.travis-opam.sh’ to ‘.travis-docker.sh’ and added ’services: -docker’, because docker has been recommended by many.

Now the build failed after some seconds. Maybe there is more to do than this trivial change to switch to docker.

Is there some documentation on how to use docker? Is it worth the effort i.e. will it run faster or has it more features?

Regards
Helmut


> On Apr 9, 2019, at 16:36, Anil Madhavapeddy <anil@recoil.org> wrote:
> 
> On 9 Apr 2019, at 19:14, Helmut Brandl <helmut.brandl@gmx.net <mailto:helmut.brandl@gmx.net>> 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:
> https://github.com/mirage/ocaml-cohttp/blob/master/.travis.yml <https://github.com/mirage/ocaml-cohttp/blob/master/.travis.yml>
> 
> 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.
> 
> regards,
> Anil


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

Re: [Caml-list] Opam packages and CI

[Louis Roché]

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

> - Is this a stable form on how to use travis with ocaml?

There is auto-ci that can be used to generate travis configuration relying on ocaml-ci-scripts.

https://github.com/yomimono/autoci

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