5 ms·

I've moved to develop most of the time on a (time-share) beefy machine on AWS, so my "locally" is always a pretty strong machine. While I develop I start a `wa

I've moved to develop most of the time on a (time-share) beefy machine on AWS, so my "locally" is always a pretty strong machine. While I develop I start a `watch` process that keeps running the tests. The watch runs a container with the docker image of the CI, mounting only my development working directory. With this setup there's no added value to the CI

wizofaus 4y ago
Well there are plenty of possible projects for which CI has no value, I don't think that's a controversial statement. But anything of any complexity with a decent size team (where a full CI build is likely to take 20 min+), then I can't imagine being convinced it wasn't needed.
HWR_14 4y ago
> I've moved to develop most of the time on a (time-share) beefy machine on AWS, so my "locally" is always a pretty strong machine. We looked at doing this, but it seemed to be pretty expensive. Like, it was cheaper to upgrade a developers machine twice a year expensive. Is that what you see or was it just setup wrong on our side?