|
From: | Éloi Rivard |
Subject: | Re: [Denemo-devel] Continuous Integration |
Date: | Mon, 21 Oct 2013 17:57:09 +0200 |
I think it is the lack of mpost etc in the host that is causing the
failure. On all the successful gub builds I have downloads/mpost is
empty, but mpost is present in the host tools. How do you set up the
host so that all the stuff is there? I had to install some texlive
package that I didn't have already to try and build from gub a while
back ... Jeremiah gave me the package name in an email a few weeks ago.
As I recall, it provided the mpost executable (on the host).
Richard
On Mon, 2013-10-21 at 16:55 +0200, Éloi Rivard wrote:
> mf and mpost are not present and this makes my build fail.
> http://denemo.org/~rshann/gub/downloads/mpost/
> http://denemo.org/~rshann/gub/downloads/mf/
> https://travis-ci.org/azmeuk/denemo/jobs/12722937#L1576
>
>
>
> 2013/10/20 Jeremiah Benham <address@hidden>
>
>
>
> On Thu, Oct 17, 2013 at 5:22 PM, Éloi Rivard
> <address@hidden> wrote:
> Hi,
>
> I recently discovered continuous integration tools,
> and this is great! The principle is to build a project
> and run some tests in different environments at each
> commit (continuously). Each build is made from a clean
> new distro image. You prepare some scripts to install
> the dependencies, and some other scripts to build the
> project and run some other tests. Then you can check
> the result somewhere, on a webpage for example.
>
> A lot of services exist: Travis, Jenkins, Wercker etc.
>
>
> This is great to easily spot regressions on projects
> that can run on several environments, such as denemo.
>
>
>
> I played a bit with Travis-ci and denemo:
> https://travis-ci.org/azmeuk/denemo . It is
> synchronized with my github account:
> https://github.com/azmeuk/denemo
>
> For the moment the only test done is compilation, but
> it is very flexible and it is possible to run some
> unit tests. Unfortunately, there is no test suite in
> denemo :). However, a good non-regression test could
> be to launch the program, check that commands are
> correctly launched for instance, and close it just
> after.
>
> It works great with gcc and clang, and fails with
> mingw as I did not prepared a good script to run.
> Jeremiah, if you want to help me there, you are
> welcome :) Your gub fork fail to download ImageMagick.
>
>
>
>
>
> This sounds interesting. I am not sure how much I can help
> because I have very little time to work on this stuff. I could
> potentially install jenkins on denemo.org but I am not sure
> what the size requirements would be. I will give it a thought
> after checking out their website and perhaps some docs. That
> is unless the travis-ci thing is better suited to our needs.
>
>
> Jeremiah
>
>
>
>
>
> The main drawback here is that Travis seem to only
> works with Github. Other repositories are available if
> you pay. To use continuous integration with denemo, it
> is either needed to use another service or copy each
> revision into a github repository. Create a
> synchronized github clone of the savannah repository
> can easily be done. Jenkins for instance is a free ci
> system, but to use Jenkins, a dedicated host is
> needed.
>
>
> Well, I would like to know your thoughts about this.
> Do you like the idea ? Which service do you prefer
> etc. Should I commit my Travis scripts to master if
> someone is interested ?
>
>
>
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/denemo-devel
>
>
>
>
>
>
>
> --
> Éloi Rivard - address@hidden
>
> « On perd plus à être indécis qu'à se tromper. »
>
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/denemo-devel
[Prev in Thread] | Current Thread | [Next in Thread] |