3 ms·
"I, for one, hope that we aren't using Jenkins in 2025" Or at least, if we are, it's a far more robust and capable system that's actually really designed for d
by wizofaus 4y ago
"I, for one, hope that we aren't using Jenkins in 2025"
Or at least, if we are, it's a far more robust and capable system that's actually really designed for dealing with all the different things that people need to do while building and testing software.
But surely most IDEs these days make it simple to run all unit tests locally? My usual M.O. is to manually run the tests locally that I believe will demonstrate my changes are "working" and rely on the full suite of CI unit tests to check I haven't broken anything else. What other options are there?
- henrydark 4y agoI'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 agoWell 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?