Hacker News Reader

Comment by dan_manges | Hacker News Reader

A new CI/CD platform. Local CLI (run without git push), remote debugger, automatic content-based caching, DAG-based definition, and dynamic tasks. It’s taken a lot of work to build it, but I’m really excited about how well it’s working. https://rwx.com/mint

View on HN

I haven't tried this yet, but I wanted to say I think there's a lot of potential in this space. There's so much friction with the current popular solutions...and yet it's so hard to justify trying some of the newer and less popular ones.

I wish you luck because there are a lot of good ideas in here. Running locally and remote debugger are the most exciting to me.

I like the idea, but I have used Azure Pipelines, and the key differentiating it from GitLab.ci is its "service connection" that enables seamless integration with third-party services and a wide range of tasks (PowerShell, pscore, az, docker, etc).

I wish your dependency semantics yaml could be converted to Azure pipeline task, job, and stage similar to how typescript converts to javascript.

I am saying this because there are very complicated infrastructural problems that hundreds of people work on at big companies when creating a ci/cd I see you are not focusing on them yet but that DAG logic could be applied to existing azure pipeline yaml.

This seems really neat! I'm a huge proponent of incremental CI for any project that gets big enough to care about test speed.

I'd be pretty worried about an abstraction ceiling on the caching here relative to something like Bazel, though. Like would Mint get mad if I generated 4000 dynamic tasks?

I love Captain! I would have been over the moon to see this project ~1 year ago when I was porting our CI away from Circle CI.

Out of interest: CircleCI also has flaky test detection, rerun failed tests etc. Or did you mean that the CI that you were moving towards could benefit from Captains features?

(disclaimer: i'm a CircleCI employee)

CircleCI was incredibly expensive. We're at 1/30th of the cost with self-hosted GitHub actions.

I didn't make myself clear I think. You mention that you love Captain, and wish you had access to it when migrating away from CircleCI. I'm interested in understanding the specific reason(s) for your love for Captain's features, that seem to also be available in CircleCI?

When we moved away from Circle we had to come up with a replacement for flaky detection.

understood, tnx!

how does it compare with dagger?

Reply on news.ycombinator.com