Travis CI integrated into GitHub pull requests thanks to new Commit Status API
1–10 of 23 posts
Re: Travis CI integrated into GitHub pull requests thanks to new Commit Status API
#2I love this a lot, but I would love this more if GitHub bought up Travis so I can do things like have Travis run on private repositories.
I'm really glad Travis has such awesome sponsors keeping them alive, but I think most paying customers of GitHub would be more than happy to pay an extra $5 a month or something to have priority queuing on Travis, and ability to run on private repos and such. With build checking brought in-house, I really don't know what else GitHub would be missing from the overall process of checking in code.
Re: Travis CI integrated into GitHub pull requests thanks to new Commit Status API
#3I love this a lot , but I would love this more if GitHub bought up Travis so I can do things like have Travis run on private repositories. I'm really glad Travis has such awesome sponsors keeping them alive, but I think most paying customers of GitHub would be more than happy to pay an extra $5 a month or something to have priority queuing on Travis, and ability to run on private repos and such. With build checking b…
It looks like Travis has a "pro" edition coming, but the link goes to a placeholder page ATM
Re: Travis CI integrated into GitHub pull requests thanks to new Commit Status API
#4I love this a lot , but I would love this more if GitHub bought up Travis so I can do things like have Travis run on private repositories. I'm really glad Travis has such awesome sponsors keeping them alive, but I think most paying customers of GitHub would be more than happy to pay an extra $5 a month or something to have priority queuing on Travis, and ability to run on private repos and such. With build checking b…
I love Travis as well and use it on a lot of open-source projects I'm a contributor to, but I've been using CircleCI for private repos so far and really love what they do. I'd absolutely recommend checking it out: https://circleci.com/
It'll be interesting to see how the hosted CI market takes off - I thought CloudBees was going after it for awhile, but it seems they haven't pushed too hard, while there have been a lot of new entrants over the past year. Good time to be a developer, that's for sure.
Re: Travis CI integrated into GitHub pull requests thanks to new Commit Status API
#5I love this a lot , but I would love this more if GitHub bought up Travis so I can do things like have Travis run on private repositories. I'm really glad Travis has such awesome sponsors keeping them alive, but I think most paying customers of GitHub would be more than happy to pay an extra $5 a month or something to have priority queuing on Travis, and ability to run on private repos and such. With build checking b…
It looks like Travis has a "pro" edition coming, but the link goes to a placeholder page ATM http://about.travis-ci.org/docs/user/travis-pro/
Oh, neat!
I think there is an aspect which I didn't mention of "Who do you trust with your code?" and GitHub has done well to earn the trust of lots of great companies, but I can certainly see IT managers getting a bit ancy at adding another point of confidentiality failure by looping in Travis as well.
Re: Travis CI integrated into GitHub pull requests thanks to new Commit Status API
#6I love this a lot , but I would love this more if GitHub bought up Travis so I can do things like have Travis run on private repositories. I'm really glad Travis has such awesome sponsors keeping them alive, but I think most paying customers of GitHub would be more than happy to pay an extra $5 a month or something to have priority queuing on Travis, and ability to run on private repos and such. With build checking b…
I love Travis as well and use it on a lot of open-source projects I'm a contributor to, but I've been using CircleCI for private repos so far and really love what they do. I'd absolutely recommend checking it out: https://circleci.com/ It'll be interesting to see how the hosted CI market takes off - I thought CloudBees was going after it for awhile, but it seems they haven't pushed too hard, while there have been a l…
Agreed, we've been using https://railsonfire.com/ for our private repos - good to see the competition heating up in the space.
Re: Travis CI integrated into GitHub pull requests thanks to new Commit Status API
#7Earlier quoted context omitted.
It looks like Travis has a "pro" edition coming, but the link goes to a placeholder page ATM http://about.travis-ci.org/docs/user/travis-pro/
Oh, neat! I think there is an aspect which I didn't mention of "Who do you trust with your code?" and GitHub has done well to earn the trust of lots of great companies, but I can certainly see IT managers getting a bit ancy at adding another point of confidentiality failure by looping in Travis as well.
Maybe "Enterprise" accounts could have VMs with FDE; Travis gives them a bare image that's then encrypted w/ a user-provided key, so (barring a hostile attack on the host's memory) only the user has access to their data.
Though the same users that want such a thing are likely also running (locally hosted) GitHub Enterprise, it'd make more sense to provide a similar option for Travis.
Re: Travis CI integrated into GitHub pull requests thanks to new Commit Status API
#8I love this a lot , but I would love this more if GitHub bought up Travis so I can do things like have Travis run on private repositories. I'm really glad Travis has such awesome sponsors keeping them alive, but I think most paying customers of GitHub would be more than happy to pay an extra $5 a month or something to have priority queuing on Travis, and ability to run on private repos and such. With build checking b…
It looks like Travis has a "pro" edition coming, but the link goes to a placeholder page ATM http://about.travis-ci.org/docs/user/travis-pro/
That's right - I'm in the beta and it works really well.
Re: Travis CI integrated into GitHub pull requests thanks to new Commit Status API
#9Great to see Travis supporting Pull Requests.
At Mozilla we've been using Bot.io for several of our Github projects (PDF.js, Firefox OS, Popcorn.js, etc) since mid-2011 to launch regression tests right from Pull Requests. It's fully customizeable (runs on Windows, Linux, Mac, etc), open source, and a breeze to install:
http://github.com/arturadib/botio
We'll likely be implementing the status API very soon. Let me know if I can help at @arturadib.
Re: Travis CI integrated into GitHub pull requests thanks to new Commit Status API
#10I love this a lot , but I would love this more if GitHub bought up Travis so I can do things like have Travis run on private repositories. I'm really glad Travis has such awesome sponsors keeping them alive, but I think most paying customers of GitHub would be more than happy to pay an extra $5 a month or something to have priority queuing on Travis, and ability to run on private repos and such. With build checking b…
> I really don't know what else GitHub would be missing from the overall process of checking in code.
CI as-a-service is a massive undertaking, and requires different focus from what GitHub is currently doing. Three main differences are
1) lots and lots of devops. You have to support dozens of ruby, python, php versions. You have to support the version that Heroku uses, the one that EY uses, the one that AppFog uses. Same with databases. Then you have to somehow deal with the fact that gems that compile on Ubuntu 10.04 don't compile on Ubuntu 12.04
2) Then you have to make all of the above fast. We (I'm one of the founders of CircleCI https://circleci.com) spent months improving build speed, to make a compelling product. People don't pay for build results that take longer than their laptop can provide.
3) CI-aaS is high touch. A large percentage of new users will have lots of support in their first month. We don't track this stat yet, but Jason Cohen (founder of WPEngine) does, and his customers require 4x the support in their first month , compared to existing users.
3) Doing this well costs (and is worth) more than git hosting. It'd be a little strange for GitHub to buy a CI product, and then charge 2-10x for CI what they do for github.
4) GitHub has released multiple OSS CI products, and their employees have told me they don't think it makes sense to do hosted CI.
So I'm not holding my breath for an acquisition. But in the meantime, you can start testing on CircleCI today.