From: Gaute Hope <eg@gaute.vetsj.com>
To: Whyme Lyu <5longluna@gmail.com>
Cc: sup-talk@rubyforge.org
Subject: Re: [sup-talk] Travis integration
Date: Tue, 26 Mar 2013 23:53:12 +0100 [thread overview]
Message-ID: <515226D8.5080805@gaute.vetsj.com> (raw)
In-Reply-To: <515189B8.9050800@gmail.com>
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
prev parent reply other threads:[~2013-03-26 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sup-heliotrope/sup/pull/9/c15243758@github.com>
2013-03-26 7:11 ` Gaute Hope
2013-03-26 11:42 ` [sup-talk] " Whyme Lyu
2013-03-26 22:53 ` Gaute Hope [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=515226D8.5080805@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=5longluna@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox