From: Whyme Lyu <5longluna@gmail.com>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] Travis integration
Date: Tue, 26 Mar 2013 19:42:48 +0800 [thread overview]
Message-ID: <515189B8.9050800@gmail.com> (raw)
In-Reply-To: <51514A36.5040907@gaute.vetsj.com>
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
next prev parent reply other threads:[~2013-03-26 12:13 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 ` Whyme Lyu [this message]
2013-03-26 22:53 ` [sup-talk] " Gaute Hope
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=515189B8.9050800@gmail.com \
--to=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