Fortunately not really, in my case. I stay out of the pipelines game as much as possible and focus on systems that enable better and more obvious pipelines. And then sometimes go tune some pipelines but mostly I find them to be pretty atrocious UI and much too snowflakey.
“The build is failing. Does anyone know why the build is failing!? See, right here. It says the build failed. Can someone look into why the build failed. Why is the build failing??”
Now you’re doing pipelines forever. 😞
Fortunately not really, in my case. I stay out of the pipelines game as much as possible and focus on systems that enable better and more obvious pipelines. And then sometimes go tune some pipelines but mostly I find them to be pretty atrocious UI and much too snowflakey.
“The build is failing. Does anyone know why the build is failing!? See, right here. It says the build failed. Can someone look into why the build failed. Why is the build failing??”
10 minutes later…
“Nvm. It was something I did.”
Be me, the only one who knows how to read the ancient text of Jenkins log.
I also seem to be a member of the ancient society of log readers.
I really don’t understand why membership is so exclusive. Deciphering log messages isn’t always super easy but it usually isn’t too bad.