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.
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 :) [email protected]
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.
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 [email protected]
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.
"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."
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!
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. :)