Share
Report
5We have a CRM Dynamics 365 application running in PROD. Now we want to put 40-60 medium changes to enhance current the application, the changes are majorly on validation UI etc.
The assets we might change will be entities, java scripts, UI configurations etc.
I am wondering what is the best practices for the development and deployment process?
We have a critical issue on building the exact version as current PROD. We have some changes left at the current development environment and we need to figure out to revert the changes and doing more regression tests.
The major solution for this project is called Main solution.
For development process:
- should we build incremental builds periodically ( every Tuesday) to export Main solution and push into TEST environment to allow tester to test?
- or ask developers to build patch solutions under their name and collect all those patch solution at every Tuesday to install the patches at TEST env to test ?
For deployment process :
- Build the entire Main solution and push into STAG/PROG.
- or create a patch solution based on parent solution which is Main and only select the assets which are changes during all the Sprint cycle and install this patch solution to STAG/PROD. Of we do this way, what is the version control?
- or create a new solution and add all the assets which are changed or added into the application. ( if some developer create a new assets which are not included in the Main solution, will we have issue? we have to life-time manage this solution along with Main solution? as it becomes a required solution.
What is the best practices on setting development cycle and best practices on deployment process in this complex situation as we did not have clear copy as PROD in dev?
thanks
All responses (
Answers (
