I've worked in teams where I'm the only one who actually checks out the branch to poke around
I've worked in teams where I'm the only one who actually checks out the branch to poke around
The CI pipeline may not wholly be in your team's control. I've worked at places where a 'devops' team had too much control, liked to tinker all the time and often broke stuff. Nothing we could do - devops were gods and didn't take input from anyone.
Should I not do check it out locally and instead spend months and political capital arguing for more in the CI (which the PM would argue slows down velocity - and will win)?
Pragmatism and workarounds are often employed in non-bigtech enterprise companies...
edit: I also meant 'poke around' as in do a bit of informal QA. Again, your test and QA team might not be perfect...
A great idea, though; when we finally get automated testing in CI, I'll certainly suggest it :)
This can help you identify additional pieces of feedback that you might have missed by just reading the code in a web interface.
The worst part is the false sense of security that you get that will bite your team the second you miss reviewing a change or go on vacation