|
|
|
|
|
|
by lostcolony
2078 days ago
|
|
|
"It doesn't stop the build pipeline, but it warns you that garbage is about to come out the other end." Why doesn't it? Prevent it from merge and build; require the dev to either fix it, or convince the rest of the team that the change should be allowed. |
|
|
The API change is communicated and approved by both parties.
You build the first thing.
Canary fails, because API has changed.
You change the other to match the new API.
Canary fails again, because it uses the most recent non-failed build.
???
Owner of the canary build is now shunned.