[opam-devel] [ocaml-infra] Is there a compilation farm for OCaml open source projects somewhere?

[Sylvain Le Gall]

2013/9/18 Anil Madhavapeddy <anil at recoil.org>:
> [CCing opam-devel]
>
> It would certainly make sense to do some of it with TravisCI, but it hits
> its limits fairly quickly (non-Linux, non-x86, constraint exploration).
>
> I've been meaning to try Mike Lin's Travis/OPAM integration for ages, so
> if you get a chance to refresh his script with OPAM 1.0/trunk and give
> it a shot, I'd love to use it myself.
>
> http://blog.mlin.net/2013/02/testing-ocaml-projects-on-travis-ci.html
>
> (more testing always better, as long as someone can triage it, and Travis
> is very convenient to use indeed!)
>

+1 if someone can spend time on this. I'll add a .travis.yml to my
github project if it is possible (even though I have a running
Jenkins).

All this builder (Travis/Jenkins/ocamlot) are good to test a project
in non upstream developper environment and helps to catch obvious
error that will happen the first time someone else than the mani
developper try to build an OCaml project.

If you need tester, I am all for it.

Regards
Sylvain

> -anil
>
> On 17 Sep 2013, at 19:20, Malcolm Matalka <mmatalka at gmail.com> wrote:
>
>> Can't a lot of this be done with TravisCI?  I have not used it but I'm
>> under the impression it allows you to run whatever you want across many
>> virtualized environments.
>>
>> Amir Chaudhry <amc79 at cam.ac.uk> writes:
>>
>>> --
>>> sent via mobile
>>>
>>> On 17 Sep 2013, at 03:01, Francois Berenger <berenger at riken.jp> wrote:
>>>
>>>> On 09/17/2013 03:14 AM, Anil Madhavapeddy wrote:
>>>>> On 13 Sep 2013, at 07:47, Francois Berenger <berenger at riken.jp> wrote:
>>>>>
>>>>>> For example, are all the packages in OPAM
>>>>>> checked regularly to compile on various architectures?
>>>>
>>>> As I have some packages in OPAM (vector3, dolog),
>>>> I would like to receive an automatic e-mail if one of my packages is broken on some arch.
>>>
>>> Since we're using GitHub in the workflow and plan to update the pull request thread with OCamlot comments, anyone involved in (or watching) the PR thread would automatically receive updates via GitHub. We need stable links for this to work properly.
>>>
>>> You can get an idea of the workflow via the screen cast I made earlier this year:
>>> http://vimeo.com/61768273
>>>
>>>
>>>
>>>>> There is; see my recent write up on its status here:
>>>>> http://anil.recoil.org/2013/09/09/ocamlot-autotriaging.html
>>>>>
>>>>> We're working on making the results more easily accessible via
>>>>> permalinking and archiving, but for now the results are triaged
>>>>> by me in OPAM bugs such as:
>>>>> https://github.com/OCamlPro/opam-repository/issues/1029
>>>>>
>>>>> Fixes to any of those most welcome!
>>>>>
>>>>> -anil
>>>>
>>>> _______________________________________________
>>>> Infrastructure mailing list
>>>> Infrastructure at lists.ocaml.org
>>>> http://lists.ocaml.org/listinfo/infrastructure
>>> _______________________________________________
>>> Infrastructure mailing list
>>> Infrastructure at lists.ocaml.org
>>> http://lists.ocaml.org/listinfo/infrastructure
>> _______________________________________________
>> Infrastructure mailing list
>> Infrastructure at lists.ocaml.org
>> http://lists.ocaml.org/listinfo/infrastructure
>>
>
> _______________________________________________
> opam-devel mailing list
> opam-devel at lists.ocaml.org
> http://lists.ocaml.org/listinfo/opam-devel