3 ms·
Once upon a time, builds used to be very expensive and take forever. Entire development teams shared a single single-pipe build server, and builds could not eve
by vorpalhex 9y ago
Once upon a time, builds used to be very expensive and take forever. Entire development teams shared a single single-pipe build server, and builds could not even be built locally first.
We're (mostly) past those times now, but "breaking the build" is still in the mind of many devs as a negative behavior.
- aeorgnoieang 9y agoI'd imagine 'breaking the build' is, for almost everyone nowadays (and in most situations), a very minor issue. But it's still, all else equal, a net negative, however small. Breaking a build once, for whatever reason, probably isn't a big deal. But breaking a build frequently certainly could be.
- sli 9y agoIf you break our build, your pipeline fails and your code is not merged. Simple as that. The master branch doesn't break, because we don't merge broken code into it.