[erlang-questions] Continuous Integration and Release Management for Erlang projects

[Jon Watte]

Most integration servers will simply allow you to trigger scripts when
commits are made in source control, and then check the exit status of that
script for success/failure.

We use the buildbot project for all of our build automation at IMVU, which
spans half a dozen languages, including Erlang. The script is basically
"svn update" followed by "make test-all" so all the Erlang-specific work
happens in the make system.

Sincerely,

jw


--
Americans might object: there is no way we would sacrifice our living
standards for the benefit of people in the rest of the world. Nevertheless,
whether we get there willingly or not, we shall soon have lower consumption
rates, because our present rates are unsustainable.



On Wed, Dec 21, 2011 at 4:13 PM, Zabrane Mickael <zabrane3@REDACTED> wrote:

> I found *Travis CI* which seems to support Erlang:
> http://about.travis-ci.org/docs/user/languages/erlang/
>
> The *etorrent* project is already there:
> http://travis-ci.org/#!/jlouis/etorrent
>
> I'd like to know if you could share your experience (*etorrent*) guys?
>
> Regards,
> Zabrane
>
>
> On Dec 22, 2011, at 12:52 AM, Zabrane Mickael wrote:
>
> Hi,
>
> Is there something equivalent to:
> *Bambou*: http://www.atlassian.com/software/bamboo/
> or
> *Jenkins*: http://jenkins-ci.org/
>
> for Erlang projects!
>
> Regards,
> Zabrane
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111221/91567161/attachment.htm>