Followup on: Other strategies for promotion management?
If you have three central repositories, it seems pretty easy that at least one or more central repositories out of sync with the others.
For example, if I move an interface into the dev-central repository, and begin testing, I might find issues which require changes. I would make them on the test-central repository, then once those changes are done and validated move them to the production central repository.
But if I forget to replace the dev-central repository after making changes on test, the dev repository will be different than test/production.
This seems like it could present issues in the future, if there is an issue with the production and someone doesn't pull from the production dev-central, first, and starts making changes to the old code in the dev-central repository.
- Are there any good ways to ensure all the central repositories always have the most updated objects (and are all identical)? Or is not really a problem? Am I missing something?