6 ms·

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 activa

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

daddykotex 8y ago
Thanks for Travis. It's great and it's is really useful, at least for our open sources project.
- cookiestack 8y ago
  Thanks for using and trusting us :)
samth 8y ago
This is somewhat related, but you mention the transition to GitHub Apps in your blog post. For those of us already using Travis via GitHub Services, what's the right way to transition to GitHub Apps?
- cookiestack 8y ago
  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
robinhood 8y ago
Thanks Josh! I've received your email announcing this move but honestly I didn't understand at first - I had to read the blog post to understand what that meant. It makes sense that you wanted to maintain a single platform instead of two. The only worry that I have is the following. At work we are using private repositories on travis-ci.com, but we've noticed some noticeable downtimes over the past year, whereas my open source repositories, including a popular one, which run on travis-ci.org, have their build processes actually way faster and more reliable (I actually haven't noticed any significant downtimes). I don't know if it's just an impression that I have or if it's something that more people have noticed. I really hope that merging the two platforms will let you provide an even better for both pro and open source users. Thank you for Travis - many open source projects would be worst without it.
- cookiestack 8y ago
  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 :)
raasdnil 8y ago
Hey Josh, biggest issue I run into is not being able to CI forks of projects, any chance this could work in future?
- cookiestack 8y ago
  This should work, if you email support@travis-ci.com we can look into it for you.
- 2trill2spill 8y ago
  Don't fork via github and just push the code to a new repo and you can add CI to that. Edit: Or maybe that's the workaround for coverity-scan, I don't remember.
asymmetric 8y ago
Hey Josh, This is unrelated, but since you're here: any chance of Travis rolling out newer versions of Ubuntu? We use Travis to test Kubernetes apps with minikube, which will stop being possible soon when minikube stops supporting systems that don't run systemd/journalctl[0]. [0]: https://github.com/kubernetes/minikube/issues/2704 https://github.com/kubernetes/minikube/issues/2704
- cookiestack 8y ago
  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.
  - Y_Y 8y ago
    This is a weird thing to say, surely you already have enough information to look into the problem. At least you were gracious enough to let them mention the chat though.
    - mikekchar 8y ago
      Not for me to say, but I suspect the issue is more that they want an internal ticket to ensure the issue doesn't get forgotten. Asking for an email will mean that it goes through their normal support channels. FWIW, I've gotten really good service asking about edge cases like this in the past.
gus_massa 8y ago
Perhaps it's still not decided, but are you going to move all the build history from travic-ci.org to travis-ci.com? Can you add an automatic redirect from the old URL to the new URL? I have a few links that say "... an it's good enough to pass all the test in Travis CI", "... but it fails miserably in the test in Travis CI".
- cookiestack 8y ago
  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.
  - gus_massa 8y ago
    I was not clear. The link is ok, travis is ok, the code in my commit is wrong :).
kuschku 8y ago
Hey Josh, An unrelated request: We’ve been waiting for a response to https://github.com/travis-ci/apt-package-whitelist/issues/1988 https://github.com/travis-ci/apt-package-whitelist/issues/19... for almost 2.5 years now, and no human ever looked at it. Is there anything we missed? Anywhere we should’ve also registered this request? Thanks
- cookiestack 8y ago
  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.
nukeop 8y ago
Is there any difference between the two services now? Or are they going to be merged under a single domain?

daddykotex 8y ago

Thanks for Travis. It's great and it's is really useful, at least for our open sources project.

cookiestack 8y ago
Thanks for using and trusting us :)

samth 8y ago

This is somewhat related, but you mention the transition to GitHub Apps in your blog post. For those of us already using Travis via GitHub Services, what's the right way to transition to GitHub Apps?

cookiestack 8y ago
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

robinhood 8y ago

Thanks Josh! I've received your email announcing this move but honestly I didn't understand at first - I had to read the blog post to understand what that meant. It makes sense that you wanted to maintain a single platform instead of two. The only worry that I have is the following. At work we are using private repositories on travis-ci.com, but we've noticed some noticeable downtimes over the past year, whereas my open source repositories, including a popular one, which run on travis-ci.org, have their build processes actually way faster and more reliable (I actually haven't noticed any significant downtimes). I don't know if it's just an impression that I have or if it's something that more people have noticed. I really hope that merging the two platforms will let you provide an even better for both pro and open source users. Thank you for Travis - many open source projects would be worst without it.

cookiestack 8y ago
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 :)

raasdnil 8y ago

Hey Josh, biggest issue I run into is not being able to CI forks of projects, any chance this could work in future?

cookiestack 8y ago
This should work, if you email support@travis-ci.com we can look into it for you.
2trill2spill 8y ago
Don't fork via github and just push the code to a new repo and you can add CI to that. Edit: Or maybe that's the workaround for coverity-scan, I don't remember.

asymmetric 8y ago

Hey Josh, This is unrelated, but since you're here: any chance of Travis rolling out newer versions of Ubuntu? We use Travis to test Kubernetes apps with minikube, which will stop being possible soon when minikube stops supporting systems that don't run systemd/journalctl[0]. [0]: https://github.com/kubernetes/minikube/issues/2704 https://github.com/kubernetes/minikube/issues/2704

cookiestack 8y ago
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.
- Y_Y 8y ago
  This is a weird thing to say, surely you already have enough information to look into the problem. At least you were gracious enough to let them mention the chat though.
  - mikekchar 8y ago
    Not for me to say, but I suspect the issue is more that they want an internal ticket to ensure the issue doesn't get forgotten. Asking for an email will mean that it goes through their normal support channels. FWIW, I've gotten really good service asking about edge cases like this in the past.

gus_massa 8y ago

Perhaps it's still not decided, but are you going to move all the build history from travic-ci.org to travis-ci.com? Can you add an automatic redirect from the old URL to the new URL? I have a few links that say "... an it's good enough to pass all the test in Travis CI", "... but it fails miserably in the test in Travis CI".

cookiestack 8y ago
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.
- gus_massa 8y ago
  I was not clear. The link is ok, travis is ok, the code in my commit is wrong :).

kuschku 8y ago

Hey Josh, An unrelated request: We’ve been waiting for a response to https://github.com/travis-ci/apt-package-whitelist/issues/1988 https://github.com/travis-ci/apt-package-whitelist/issues/19... for almost 2.5 years now, and no human ever looked at it. Is there anything we missed? Anywhere we should’ve also registered this request? Thanks

cookiestack 8y ago
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.

nukeop 8y ago

Is there any difference between the two services now? Or are they going to be merged under a single domain?