The new pricing model announcement on HN:
Travis CI's new pricing plan threw a wrench in my open source works
81–90 of 148 posts
Re: Travis CI's new pricing plan threw a wrench in my open source works
#82Did not know about the pricing change (no email or any attempted communication it seems). Will be moving to GH actions immediately, bye bye Travis.
Re: Travis CI's new pricing plan threw a wrench in my open source works
#83Earlier quoted context omitted.
This "one guy," if you will, is responsible for a majority of the ansible galaxy modules that are out there. Far from a bad actor just utilizing CPU time for pet projects, Jeff's code is probably in use in a large majority of companies that use Ansible, mine included.
How much money does your company contribute to Jeff?
100% this! People can’t possibly complain when companies charge for their tools. If an open source project is important to an organisation, they better start donating.
Re: Travis CI's new pricing plan threw a wrench in my open source works
#84Travis is trash anyway. I've switched to CircleCI years ago and I'm happy with it. Also completely free. PS: I'm in no way affiliated with CircleCI, I'm just a happy customer.
Re: Travis CI's new pricing plan threw a wrench in my open source works
#85Earlier quoted context omitted.
Run it in a docker container so that it does the same in your computer and in the CI worker. make prepare make build make test make release Working the same waylocally and in jenkins makes things very easy. What it does is up to the team but make prepare usually pulls some docker image and install dependencies, make build builds something inside the docker image, make test runs test inside it and make release publish…
Or use a CI/CD tool that natively supports Docker, like Concourse. Added bonus is that pipelines are defined in YAML rather than web GUI so you can version control the pipelines themselves and not just any build or test suites.
Jenkins pipelines are written in Groovy and you do not need to use the web ui, everything is exposed via its API (i.e: new job creation).
I have heard good things about Concourse, want to give it a try in the future!
Re: Travis CI's new pricing plan threw a wrench in my open source works
#86It seems to me if it takes you many hours to migrate your project from one CI provider to another you're doing things wrong.
Ultimately your .travis.yml file is a proprietary format for a service that you have no control over. You probably shouldn't have built your project's future on the assumption that it's always available.
Ideally you should have your own testing infrastructure in scripts or test frameworks. And your travis file shouldn't do much more than installing dependencies and running the stuff that's under your control. Put all the logic into the stuff you can control - and next time you find out that your favorite CI provider is no longer nice to you you simply use another one, the migration should not take more than a few minutes.
Re: Travis CI's new pricing plan threw a wrench in my open source works
#87The travis-ci.org website still lists this lol,
"Testing your open source projects will always be free! Seriously. Always. We like to think of it as our way of giving back to a community that connects so many people."
Re: Travis CI's new pricing plan threw a wrench in my open source works
#88The travis-ci.org website still lists this lol, "Testing your open source projects will always be free! Seriously. Always. We like to think of it as our way of giving back to a community that connects so many people."
My heart skipped a beat. Why is it extremely difficult to be honest about wanting to make a profit one day?,
Re: Travis CI's new pricing plan threw a wrench in my open source works
#89Earlier quoted context omitted.
Github Actions really is a freakin awesome product. Yeah, there's lock-in, but their free plan (and cheap Pro plan for individuals) offers a great value. And, really, CI is CI; if you ever need to migrate, even for this guy with hundreds of projects it should only take a couple days. Once you've seen one CI yaml file, you get the gist of what all of them do. Other options: * Gitlab CI. Good value, great integration w…
I'm quite happily using a self-hosted Drone (drone.io) instance, though I don't have much experience to compare it with with other CI systems and my use case is probably not the most sophisticated one. Team is quite responsive, especially considering I'm a free tier user.
I really like Drone. The way “drone exec” works for local builds is really good. Hopefully getting bought by Harness doesn’t ruin it too much, but they already seem to be setting up to split it into versions/tiers.
Almost all current CI systems suck at building Docker containers :-(
Re: Travis CI's new pricing plan threw a wrench in my open source works
#90I've been using Travis on a bunch of my opensource projects and was wondering why builds were getting queued for ~a day before they'd run, I guess I got my answer. :/ I don't really want to lock myself into GH actions (ideally, I wouldn't be on GH at all), does anyone have any suggestions for alternatives? I don't mind paying some money, but the almost $1K/year for Travis' lowest tier is about an order of magnitude m…
Azure Pipelines has been really good for us. Much much more reliable than travis, and decent pricing. For self-hosted, I've heard really good things about build-kite ( https://buildkite.com/ ) although I've not used it myself.
I can’t see where build-kite is self hosted. It seems like you must use their SaaS dashboard which makes it DOA for me.