Re:How a Jenkins Job Broke our Jenkins UI
by hinkley on Thursday June 03, 2021 @11:29PM
(#27390252)
I think it's a frog boiling problem.
I start with building my code, then deploying it, then verifying the deployment, a few smoke tests, regression tests, pretty soon all of those concepts are crowding in on the brainspace of monitoring.
It's just one more thing, why slow down to learn a new tool and convince people to use it?
These days it's getting easier for me to requisition a machine to run a dev tool on. That hasn't always been the case, and I'm sure it's not the case everywhere.
I start with building my code, then deploying it, then verifying the deployment, a few smoke tests, regression tests, pretty soon all of those concepts are crowding in on the brainspace of monitoring.
It's just one more thing, why slow down to learn a new tool and convince people to use it?
These days it's getting easier for me to requisition a machine to run a dev tool on. That hasn't always been the case, and I'm sure it's not the case everywhere.