3 ms·
Does this matter that much if you version everything? Commit in library -> successful library build, failed client build. Commit in client -> successful librar
by oblio 13y ago
Does this matter that much if you version everything?
Commit in library -> successful library build, failed client build.
Commit in client -> successful library build, successful client build.
In both situations you don't really care about the intermediary broken build - you still have the previous library/client versions and can use those. Once everything is committed & fixed you have the new versions and you can upgrade.
The only problem I see if there's a long delay before the second commit. But this can be prevented by a fast CI cycle (always a good idea) and sending notifications for failures across teams (i.e. the library committer is notified
that the client build for his commit failed).
- zaphar 13y agoIf you care about how long it takes to make the change in all your code bases and you care that you identified all the code that needed to change did change then it matters.