I'm having a very similar issue getting https://brisktest.com/ out there. People complain about things like the speed of their build system, but convincing people that your CI system is faster just seems like an uphill battle. Maybe the era of launching new indie dev tools to developers is over and you just need a massive marketing budget to bombard devs with advertising and lots of sponsored content. - Source: Hacker News / 12 months ago
Hi everyone, I'm Sean I'm the creator of Brisk a new CI/CD tool. I'd love to share a little bit about it with the community and get any feedback you might have. Source: about 1 year ago
Paul, if you are interested in speeding up your tests for either Bun or Jest you might be interested in checking out my latest project. At Brisk we keep pre-built workers for your project in our infrastructure so there is no build time that eats in to your test time. This also means there isn't as much of a concurrency penalty that you get with traditional CI services (scaling up to 30 workers only to spend 30... - Source: Hacker News / over 1 year ago
We've had a lot of success with Brisk (https://brisktest.com/) doing this exact thing. It keeps our environment running so we don't have to rebuild on every run, kind of like a dev build. It's really fast. - Source: Hacker News / over 1 year ago
Super interesting you mention “local first CI”. Have a look at Brisk https://brisktest.com/ (I’m the author). It’s designed to work “locally” pre-commit, giving you super fast tests, but then when you push you can also use it in your CI/CD pipeline. We achieve the speed with massive concurrency and pre-built environments, it was built as a drop in replacement for your local test runner. - Source: Hacker News / almost 2 years ago
> the model of CI where a totally pristine container (or VM) gets spun on each change for each test set imposes an floor on how fast CI can run I believe this is the motivation behind https://brisktest.com/. - Source: Hacker News / almost 2 years ago
Put simply we use pre-built environments and massive parallelization to run test suites in seconds (you can see demos here). I'd love for members of the community to give me any feedback that y'all might have. I know you are an opinionated bunch so any and all feedback greatly appreciated. Source: almost 2 years ago
It's interesting to see CI wait times as core engineering metric. I 100% agree, so much so that I'm building a product specifically to speed up CI. We have redesigned how hosted CI works focusing on speed as our north star. We don't have CI wait time - your test starts immediately and we run your tests super fast. How do we do it? We have many workers with your test environment pre-built so we can split your tests... - Source: Hacker News / almost 2 years ago
I've built a service in Go to speed up tests (https://brisktest.com/). Source: almost 2 years ago
Do you know an article comparing Brisk to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Brisk. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.