3 ms·
It's not so clear cut. Most places I've worked, we don't build artifacts (docker images, whatever) until there's a merge to master or a tag has been pushed. Thi
by ljm 6y ago
It's not so clear cut. Most places I've worked, we don't build artifacts (docker images, whatever) until there's a merge to master or a tag has been pushed. This automatically means that even though your tests remain green, you still want the status check for the stuff that isn't relevant inside a PR.
For us, if the status is red in master, it doesn't mean the code is wrong, it means something went wrong in the deploy pipeline.
- JoshTriplett 6y ago> Most places I've worked, we don't build artifacts (docker images, whatever) until there's a merge The projects I've worked on have used a bot for merges, and that bot handles building artifacts. In some cases, there's a lighter CI for "this looks reasonable", and then the full CI (including building artifacts and running more extensive test suites on every supported platform) runs before merging.