From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eg@gaute.vetsj.com>
Received: from [192.168.1.42] (216.89-20-249.enivest.net. [89.20.249.216])
        by mx.google.com with ESMTPS id i3sm7359593lbn.0.2013.03.26.15.53.28
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Tue, 26 Mar 2013 15:53:29 -0700 (PDT)
Message-ID: <515226D8.5080805@gaute.vetsj.com>
Date: Tue, 26 Mar 2013 23:53:12 +0100
From: Gaute Hope <eg@gaute.vetsj.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: Whyme Lyu <5longluna@gmail.com>
CC: sup-talk@rubyforge.org
Subject: Re: [sup-talk] Travis integration
References: <sup-heliotrope/sup/pull/9/c15243758@github.com> <51514A36.5040907@gaute.vetsj.com> <515189B8.9050800@gmail.com>
In-Reply-To: <515189B8.9050800@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Great. #12 is merged. When the 'test' target is ready I think we should
merge the Travis stuff too.

By the way; I have set 'develop' to be the default branch in github.
This will make things work more seamlessly (including closing
issues/pull request from commits and 'develop' as the default target for
pull requests).

Regards, gaute

On 26. mars 2013 12:42, Whyme Lyu wrote:
> On 03/26/2013 03:11 PM, Gaute Hope wrote:
>> What do you think about including the few files that are in the main
>> repositories?
> 
> Continuous integration is a widely adopted best practice now. A big +1
> from me.
> 
>> @Whyme: How does your Travis integration work with the new 'test' target?
> 
> Currently I'm just running `rake gem` on Travis. But it's dead easy to
> define a custom rake task to test + package anyway. I just opened
> https://github.com/sup-heliotrope/sup/pull/15 for this.
> 
> Two little issues for now:
> 
> * I'm still figuring out required dependencies to get tests running.
> This could be done soon.
> * Pull request #12 should be merged before `rake gem` could work.
> 
> -whyme
> _______________________________________________
> sup-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk