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

[Zabrane Mickael]

Thanks guys for these useful feedbacks.

Jenkins seems to be the way to go for me.

It's well documented and there's an O'reilly book "Jenkins: The Definitive Guide (2011)" available:
http://www.amazon.com/Jenkins-Definitive-John-Ferguson-Smart/dp/1449305350

Regards,
Zabrane

On Dec 22, 2011, at 7:19 PM, Magnus Klaar wrote:

> Hi!
> 
> The configuration got lost when i relocated my server to the city dump and switched laptop, I didn't see a future need for either copy of the configuration and scripts. Jenkins is quite easy to set up for simple builds, in that setup we added "prototype" project for etorrent and made a copy for each platform and erlang release we were interested in, the copy was assigned to build at a matching slave (the slaves each ran a build slave process to receive the jobs). Now that we have kerl, it's a lot easier to pull that off.
> 
> MVH Magnus
> 
> On Thu, Dec 22, 2011 at 10:26 AM, Zabrane Mickael <zabrane3@REDACTED> wrote:
> Hi Jesper,
> 
> Thanks for these feedback.
> 
> > Before Travis CI, Magnus Klaar did a jenkins setup that also worked very well for us.
> 
> Is the setup for Jenkins available somewhere?
> 
> Regards,
> Zabrane
> 
> _______________________________________________
> 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/20111222/e0e94a62/attachment.htm>