How do companies handle proxy deployments in multi-team projects?

We're currently working on a large API programme that has five different development teams. We're starting to see deployment clashes when it comes to Apigee due to the different delivery cadence of the teams, and I am wondering how other teams in other companies deal with this?

Example:

* Team A adds a flow to the proxy.
* Team B adds two flows to the proxy (on top of Team A's).
* The changes made by Team B need to be deployed to production, but Team A are not finished testing their changes yet.
So, we have to remove Team A's flows before we can deploy to Prod. We can do this using Revisions, but doing this across five different teams, with multiple changes, is proving to become a headache.

Any suggestions?

0 0 45
0 REPLIES 0