You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, I support only 1 DEV environment for 1 solution.
With a large team of multiple makers, working maybe on different environments (Dataverse) but on the same solution
What could be great ?
Support an automatic get latest version to retrieve latest code each day/week etc... in unmanaged, there are already pipelines from ALM Accelerator to delete unmanaged solution and repush it with latest version
If multiple makers (like maker1 and maker2) have their own dedicated Dataverse (Dev1, Dev2) , and they work on Solution named "XYZ" , they can have done multiple changes on different types of requirements (like maybe adding a new table, other can have done creating a new workflow etc...) : Goal will be => we use automation ALM to let's say for each deployment have the ability to NOT just have 1 dedicated environment of DEV but multiple. In this case only, we commit solution from their DEV (for each), making a TEMP branch for each of them, we made a Pull Request step by step to auto merge the code. If conflict, we can't go deeper in the flow but if all is good, it's now this one that will be pushed for validation (PR again) then Test into the SolutionBranchName. Now after, we can sync back the SolutionBranchName to their dedicated environment of DEV (get latest) to work again at the same stage of code - like discuss in the point 1./
The text was updated successfully, but these errors were encountered:
Right now, I support only 1 DEV environment for 1 solution.
With a large team of multiple makers, working maybe on different environments (Dataverse) but on the same solution
What could be great ?
The text was updated successfully, but these errors were encountered: