Move off jenkins about infra HOT 6 CLOSED

@whyrusleeping @chriscool thoughts?

from infra.

First, yeah it is a good idea to test every commit as much as possible, at least as long as it doesn't take too much time.

If Travis works well, it looks like a good idea to do as much as possible using it.

Can FUSE tests be done on Travis too?

As some tests cannot be done on Travis, maybe we can keep Jenkins only for these tests or use something else like http://buildbot.net/.

from infra.

could take a look at teamcity: https://www.jetbrains.com/teamcity/

from infra.

i'd prefer a service (that we don't have to manage) and something very
tightly integrated with the open source workflow.

On Wed, Apr 1, 2015 at 1:53 PM, Jeromy Johnson [email protected]
wrote:

could take a look at teamcity: https://www.jetbrains.com/teamcity/

—
Reply to this email directly or view it on GitHub
#9 (comment).

from infra.

I think we should:

• try to do it all on travis first, have that as something to fallback to always.
• from there, we can see about circleci and codeship, which both claim to integrate with github + open source well.

from infra.

closing in favor of #20

from infra.