| I've also tweeted about this the other day: https://twitter.com/fulopattila122/status/132098641078723379... I'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 :) |