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

Re:Travis CI's new pricing plan threw a wrench in my open so... by emptysea on Friday November 06, 2020 @12:22AM (#25005146)

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

[ Parent | on HN ]

Re:Travis CI's new pricing plan threw a wrench in my open so... by brabel on Friday November 06, 2020 @01:41AM (#25005514)

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).

[ Parent | on HN ]

Re:Travis CI's new pricing plan threw a wrench in my open so... by hinkley on Friday November 06, 2020 @11:17AM (#25008719)

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.

[ Parent | on HN ]

Re:Travis CI's new pricing plan threw a wrench in my open so... by moonbug on Friday November 06, 2020 @04:42AM (#25006379)

sweet summer child.

[ Parent | on HN ]

Re:Travis CI's new pricing plan threw a wrench in my open so... by qppo on Friday November 06, 2020 @01:04AM (#25005328)

I have a lot of ideas (or rather, one idea) about how to fix my CI problems and "fancy build system" is pretty apt. Bazel is the closest thing I've seen to what I want.

[ Parent | on HN ]