I am in the process of building out a data services migration strategy and wanted to get some insight from others. We have a four-tier data services landscape (dev, staging, QA, prod) to match our SAP R3, BW, and HANA landscape. We currently have an individual local repository in dev for each developer (38 and counting) and a single repository in staging, QA, and Prod. Each environment also has a secured central repository to hold the latest version in each environment.
The attached visio is a high-level for what I have come up with for new and existing development. Essentially the developer is reposnible for creating the code, testing, uploading to central in each environment. The admins are responsible for migrating the code from central to the local on the next environment and configuration in the new environment. My concern is having too many people logged into a single repository at the same time. Could this corrupt the repository?
My other thought was to have the developers just be responsible for development and scheduling of jobs through the data services managemnt console in each environment and the admins be responsible for migration, configuration, and uploading to central in each environment.
Any thoughts or feedback on these approaches would be appreciated.
Thanks,
Ken