It's a good thing you chose to keep one publisher. Solution Components Mover proposed by Daryl will help you a lot in your case and it is such easy to use.You said you already have version control for your solutions. Are you using Azure DevOps Server (previously named TFS)? In that case, Dynamics 365 Build Tools can help a lot in automating your process. For example you could have this process when a developer want to push it's changes to the main solution :
- copy solutions components in main solution- export main solution and extract it in a new git branch- create a pull requestThen you could easily check their changes in the pull request. and keep track of changes history.Good job of taking care of ALM best practices in your environments!Best Regards,
"Does it worth the effort to set those processes up? Even for a small team with few developers?"Having a perfect ALM process can take a lot of time for small teams so not always worth it.
Yet little things can be easily set up. And i would say that using version control is a must have even for small projects.Using Clone a patch for exemple is an easy builtin way to have a separate solution for each change.Before a release, just use Clone Solution, then export solution, extract code and but it in Git
This can be done manually at first then easily automated
If you've found this thread useful, dive deeper into User Group community content by role