Our team has just started using source control to manage the source code, we have multiple scrum teams which work in various projects. Current environment setup is one shared development sandbox, one integration testing sandbox, three UAT for different monthly release (align with other integrated system release), one stage and production. A development team is planning to deploy their work for next month release from the integration branch merge into UAT branch and then deploy the work into UAT org. So QA team can start testing. We are in Agile model and the same development team is also working their iteration work in developer sandbox then continue pushing the iteration work in integration testing environment for integration testing by QA. Now this integration testing org and integration branch have contained the next month release codes and iteration codes. When UAT testing starts, and defects have been discovered. How can we (release management) mitigate the risk of the developer won't potentially carry the iteration work when they fix the next month release defects in integration testing org. What's the best pracitce for handling this situation? Where should developer run the unit test for the fix but won't affect the iteration work?
2
-
Your branching strategy sounds a bit off, and shared dev sandboxes is a bad idea; each should get their own. It sounds like you have quite a bit of process to review and correct.– sfdcfox ♦Commented May 17, 2018 at 4:21
-
maintenance is a challenge for release and environment management team, the team doesn't just build SF codes they also build Vlocity codes. If developer has its own sandbox the environment might be always out of sync.– R.SparkCommented May 17, 2018 at 4:26
Add a comment
|