cookiestack

Travis CI will become one platform later this year. We will have more to share on this move soon. Until then everything will work as is, and we will continue to support open source on travis-ci.com going forward. Software development is something we love, and we will to continue to help the community build better software :)

I'm sorry for this long wait, this needs to be addressed. I'd love to find the right person to look into this, if you can email support and mention me (Josh) I can see if we can provide you an answer to this.

That is the plan, move and redirect. That work is in the works. We will have more blog post on this soon :)

As for the links, can you send more info to support@travis-ci.com and we can look into this.

Thanks for the ping about this. Could you email support@travis-ci.com and we can look into this for you. Feel free to also mention that we chatted here.

Thanks for the feedback. I can promise you we are looking into this, and hope to have updates on these issues in the near future :)

This should work, if you email support@travis-ci.com we can look into it for you.

Thanks for using and trusting us :)

When you go to your settings you can 'activate and migrate' your user account or organization accounts to GitHub Apps. We will switch your service hooks to GitHub App service hooks in the process. Our support team is also more than happy to help :) support@travis-ci.com

Thanks for the feedback. I'm sorry for the downtime issues you have experienced lately. I'll follow up with the team on this to understand some of the affected your projects.

This single platform change will allow us to better focus on speed improvements for all users.

Thank you for using and trusting us :)

Hello, Josh from Travis CI here.

We are happy to announce that you can now run open source projects on travis-ci.com. At the moment you can only add and activate repositories which haven't been tested on travis-ci.org. We are hard at work to add a way for you to migrate your projects from travis-ci.org to travis-ci.com, and should have more information to share on this soon.

If you have any questions I would be happy to help answer them here, or you can email our team at support@travis-ci.com

We are sorry for the recent issues, we need to do better at communicating changes to the VMs and .travis.yml processing. Thanks for the feedback :)

Hey David,

We are in the process of adding Windows support, we don't have an ETA just yet, but it is definitely in our sights! Also, the build timeout is 50mins, with a 10 min no-logs timeout.

Thanks,

Josh

Also http://about.travis-ci.org/docs/

From the love website:

"Continuous Integration for the Open Source Community"

"Travis CI has run 757,465 tests for 10,844 open-source projects to date, including Ruby, Rails, Rubinius, Rubygems, Bundler, Leiningen, Parrot, Symfony, ... If you use any of these then you benefit from Travis CI."

Hey Netmute,

We are working actively on this right now, and should have some updates in the next couple of weeks.

If you can bear with us I am sure you won't be disappointed :)

Josh

Sure, you can find me in #travis on freenode, my handle is josh-k :)

Jenkins is great for in-house installs, but Travis is currently focused on testing open source projects in a distributed and live fashion. They are not competitors as they are solving different issues. Testing open source in the open means other devs can get involved and help out when they see failures on particular setups. And you can even link to line numbers in the Travis logs, making it easier to point to the failure!

Not yet, but in the near future. It would be awesome to run the tests of projects automagically when a dependency is updated! :)

It is one of the eventually goals, but Travis has a lot of moving parts due to its distributed nature. We do plan to make in-house installs easier in the future.

You are right, and we mention that in the blog post. CPAN Testers is about testing your releases, but Travis is about testing your pushes to GitHub as you develop. Travis does not aim to replicate with CPAN Testers does, we are more of a complimentary service. :)

Travis is an open source CI system for running open source projects on. It uses a distributed setup to run the tests of projects in a sandboxed environment. The VMs also provide multiple lang versions so you can test your library against several ruby/python/perl/node/erlang/php versions without even having to think about it.

In short, Travis makes CI testing easy and fun for OS projects.

hahaha, thanks Jay, and nice plug ;)

zing!

I <3 this news, especially as we are happy users of Ember.js :)

Hey theatrus,

Travis is similar to Jenkins, but also very different.

For instance:

1. Every build is run in a virtual machine sandbox so other projects tests won't affect yours (eg. files or dbs left over).

2. The full infrastructure is distributed, the web frontend has been decoupled from the workers completely.

3. All push information sent by GitHub is built by default, so no need to tell Travis to build a certain branch.

4. We use web sockets so you can see the results in realtime.

5. Hosted for free for the open source community.

The core goal behind Travis is to make it easy for open source projects to test against different environments (language versions, databases, services, env vars etc.) with the aim to increase code quality for everyone.

So comparing Jenkins and Travis (the service) is a little like comparing apples and oranges, even though they do have a lot in common.

Hope this helps,

Josh

I guess you mean the status images? Docs can be found at http://about.travis-ci.org

Here is the page on the status images : http://about.travis-ci.org/docs/user/status-images/

Sorry, how do you mean?

If there is something we can improve feel free to add a GH issue, jump into #travis on freenode, or fork and send a pull request :)

I noticed that when you refresh the page, you can revote, do you do any checking to make sure people can only vote once?

Hey David,

I really like what you have done, a nice twist on the ol' like button. And its a pretty cool looking site as well.

One thing does, well, concern me a bit, and its that you haven't given credit where credit is due (http://jeffkreeftmeijer.com/2010/experimenting-with-node-js/).

There is no doubt that this is very similar to Jeffs blog post, and although it takes the idea a step further, I do think you should at least add a link to any and all code which inspired you and which you took ideas from, if it be Jeffs previous post, or a Node Knockout project.

Best of luck with getting Valves attention, and you have my pointers vote :)