What's up with travis ci open source builds
I am very appreciative of all the CI providers do to support open source projects. They make massive resources available at no cost. Without travis, circleci, azure pipelines, appveyor, github actions, and many other smaller services, open source could not afford to test and build.
With that, over the past week we have seen a massive backlog of linux jobs on travis. Here is the status page https://www.traviscistatus.com/#month. In the past, travis added resources when the backlog grew, but now it seems capped at 555. Does anyone know if this is a temporary glitch or if it is permanent? The support forum threads have hints this may be connected to the move from travis-ci.org to travis-ci.com, (like the comment in this thread https://travis-ci.community/t/builds-hang-in-queued-state/10250/9) but does that mean the status page is only for travis-ci.org?
3 comments
[ 2.9 ms ] story [ 20.6 ms ] threadI've found this HN thread, and thanks for your link - I've figured it out that a) there's a migration going on at Travis b) I am affected and I have to migrate until Dec 31.
I don't know what the folks at Travis are doing, but I haven't received any notification about these changes. Is "dimming the light" the way they communicate?
I would definitely pay for them to keep my Open Source builds up and running. I evaluated their paid plans a few times, but their pricing really sucks. At the open source plan I (used to) have 5 concurrent jobs. That costs $0. If I would buy the $69 plan I would have 2. So if I start paying I'll face an immediate 60% performance penalty.
I tried to "migrate" to .com today, and I bailed out. It is not taking my existing .org settings into account at all. It just connects to my github account and enables all my repositories for travis.
That is definitely not what I want. I'm working with 5 Github organizations and have access to 100+ repositories. It took me years to set up everything at travis-ci.org: - hand selected repos that are enabled - build badges linking to .org repos added to README files - webhooks in the github repos - notifications and slack webhooks
I don't know what their plan is, but they managed to piss me off. I live in Berlin and their office is about 10 minutes from here. I'm thinking to visit them for advice :)
1. Go to the old (.org) link, eg https://travis-ci.org/github/<your-org-name>/<repo-name> 2. Change "org"->"com" in the URL (leave the rest intact) and hit ENTER 3. Travis will load the page and display "Migrate" button. 4. Hit the migrate button 5. Do this with all the repos within the organization you want to migrate. 6. Some repos will complain they can't be accessed/migrated. Note them down for step 11. 7. The repos you migrated will shop up under "legacy" integrations 8. Go to https://travis-ci.com/organizations/<your-org-name>/reposito... 9. On the repositories tab, click the green "Migrate" button. 10. This will take you to the Github integration and pre-select the repos you've migrated. 11. Add manually any repo you couldn't migrate at step 6. 12. Activate the integration 13. Go back to https://travis-ci.com/organizations/<your-org-name>/reposito... 14. The ones you could migrate will show up, the ones mentioned at step 6 will not. 15. Go to the "Migrate" tab: the missing repos will show up there 16. Selected them and click migrate. You're done.
Notes: - The build history will be taken over except for repos mentioned at step 6. - The old .org github webhooks will be kept in the github repo. I removed them manually - If you have any badges (eg. shields.io) or links to the build page, the URLs need to be updated accordingly
Ps.: I would be still happy to pay for Travis, even though I only use it for open source.