Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Handle multiple developers on multiple environment working on the same solution #8

Open
AurelienClere-365 opened this issue Aug 23, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@AurelienClere-365
Copy link
Owner

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 ?

  1. 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
  2. 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./
@AurelienClere-365 AurelienClere-365 added the enhancement New feature or request label Aug 23, 2024
@AurelienClere-365 AurelienClere-365 self-assigned this Aug 23, 2024
@AurelienClere-365 AurelienClere-365 added this to the November Release milestone Aug 23, 2024
@AurelienClere-365 AurelienClere-365 moved this to Backlog in Automation ALM Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant