Live data from Hacker News

Travis CI's new pricing plan threw a wrench in my open source works

jeffgeerling.com

131–140 of 148 posts

Re: Travis CI's new pricing plan threw a wrench in my open source works

#131
post #77

Earlier quoted context omitted.

Sounds like your describing what I like to call a fancy build system Something like Bazel[0], Buck[1] Pants[2], etc. One of their main features is robust caching of build artifacts, which is helpful for larger projects. But they require some major investment compared to your typical `scripts/build.sh`. [0]: https://bazel.build [1]: https://buck.build [2]: https://www.pantsbuild.org

Gradle can also do everything imaginable, we've managed to get rid of basically all our horrible bash scripts and wrote most build stuff using Gradle API and using a proper programming language (put actual code in Gradle's buildSrc/, only configure it in build.gradle, and you've got a extremely powerful build).

Shebangs are also your friend, if your primary language can be used that way.

The cons of that solution are that there’s a tendency to make them ornate, and the trap of circular dependencies. Reusing an internal library in your build scripts, you have it building itself which can get out of hand quickly.

Re: Travis CI's new pricing plan threw a wrench in my open source works

#132

Oh boy, I just moved my projects from travis-ci.org to travis-ci.com after the builds stopped happening on .org. (Despite the travis FAQ that said "we’re making a number of changes to the travis-ci.org infrastructure to ensure the service will remain as reliable and available to you as it always has been until [it goes away Dec 31]", that was not the case, builds simply stopped working on .org. https://docs.travis-ci…

Lately as I’ve been getting (more) frustrated with Bamboo and spending time noodling with kubernetes and JAMStack. I keep flirting with the notion that there’s a new generation of CI tool out there waiting to be discovered, one that steals a bit of brain- and problem-space from all three.

One that could more easily be set up by individuals, making it amendable to open source, possibly with some small degree of federation.

Re: Travis CI's new pricing plan threw a wrench in my open source works

#133
post #9

I'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…

GitLab CI

Re: Travis CI's new pricing plan threw a wrench in my open source works

#134
post #133
post #9

I'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…

GitLab CI

I always had insane amounts of queue time on gitlab's CI too. I know they have self-hostable runners, do you know if those work from behind a firewall so I could run them on hardware I have at home?

Also, do you know if it's possible to use gitlab CI as a merge gate on github PRs?

Re: Travis CI's new pricing plan threw a wrench in my open source works

#135
post #59
post #9

I'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…

Sourcehut is something you might want to look at. It's modular, so you use what you use, and ignore the rest. The CI they offer makes no assumptions about where your repos might live (git is git. Who cares who the host is), and offers the stuff you might need like secrets, ssh keys, etc. The images they supply for testing actually seem more extensive than the other players. And if you really want to self-host it... G…

Interesting, I didn't know it would support pulling from other git hosts. It looks like their CI even has an API integration with GitHub at least for PRs. That's looking like a potential winner. Thanks for pointing that out.

Re: Travis CI's new pricing plan threw a wrench in my open source works

#136
post #93
post #85

Earlier quoted context omitted.

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!

> 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). There's several ways you can codify Jenkins pipelines, Groovy being just one of them. But ultimately it's secondary to the main design of Jenkins. I'm not taking anything away from Jenkins as a solution - it has been invaluable over the years. But the way we write, test and deplo…

While you’re not wrong I do use jenkins inside docker and use ansible to configure it, it is a bit different than other more modern tools but works fine.

I have yet to see other tools be as flexible (perforce , git, legacy tools, docker, 100s of workers across datacenters etc.)

Re: Travis CI's new pricing plan threw a wrench in my open source works

#137
post #98

Get a cheap server and just self host drone. It’s been rock solid for me. Although I am using GitHub actions more, drone powers all of more heavy duty docker builds.

Drone has recently been bought by Harness. Will it still be around in a year or two?

Good question. Running the old version will still work for the foreseeable future. Since it's on github Im sure someone would just fork it anyways.

Also just noticed I'm running a really old version.

Re: Travis CI's new pricing plan threw a wrench in my open source works

#138

Earlier quoted context omitted.

Are you moving to Jenkins because of the recent Atlassian license changes?

Not entirely but I think it was the straw that broke the camel's back. Apparently our journey to the cloud will have to wait.

I think there will still be a on premise version of Bamboo going forward, but all the license changes have made my company consider the possibility of moving from Bamboo to something else. That's kind of a shame, because Bamboo works really well for us.

Re: Travis CI's new pricing plan threw a wrench in my open source works

#139
post #134
post #133

Earlier quoted context omitted.

GitLab CI

I always had insane amounts of queue time on gitlab's CI too. I know they have self-hostable runners, do you know if those work from behind a firewall so I could run them on hardware I have at home? Also, do you know if it's possible to use gitlab CI as a merge gate on github PRs?

Hi there, GitLab team member here.

To answer your questions: yes, you can configure the Runner to work behind a firewall [1] and you can use GitLab CI for GitHub repos [2].

Hope that helps!

1 - https://forum.gitlab.com/t/how-does-communicate-gitlab-runne... 2 - https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/#pipe...

Re: Travis CI's new pricing plan threw a wrench in my open source works

#140
post #134

Earlier quoted context omitted.

I always had insane amounts of queue time on gitlab's CI too. I know they have self-hostable runners, do you know if those work from behind a firewall so I could run them on hardware I have at home? Also, do you know if it's possible to use gitlab CI as a merge gate on github PRs?

Hi there, GitLab team member here. To answer your questions: yes, you can configure the Runner to work behind a firewall [1] and you can use GitLab CI for GitHub repos [2]. Hope that helps! 1 - https://forum.gitlab.com/t/how-does-communicate-gitlab-runne... 2 - https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/#pipe...

Cool, thanks!
Post reply on HN