4 ms·
> - Put all build/publish/test logic in Makefiles or scripts in the repo. This means that devs can run it locally as well. This is critical! In many teams Dev
by john-tells-all 3y ago
> - Put all build/publish/test logic in Makefiles or scripts in the repo. This means that devs can run it locally as well.
This is critical!
In many teams Devs are "lazy", if any errors or weirdness happens in CI they just wave their hands and say "not a feature, not my problem". Even though they know exactly what's in the test code, the deploy code, and can see the issue.
Letting Devs see and run the CI scripts locally gives them _ownership_. They don't have to fix the issues, but they have control and understanding which radically reduces the arguments and pipeline drama :)
- roland35 3y agoIt also takes a lot less time to fix the tests locally too - rather than tweak it... push the change... oops it failed again... repeat...
- dharmab 3y agoThis still happens, but the surface area is greatly reduced to figuring out that the directory, variables, credentials, dependencies between stages, etc. are set up correctly