Power Platform Community Forum Thread Details

Hi,

I would like to enable the possibility of working on multiple features within a single solution. The goal is to allow multiple developers to work simultaneously.
For example, Developer 1 would work on Feature X, while Developer 2 would work on Feature Y. These features are complex and will be deployed to TEST environments in different release windows.

Current Setup:

Environments: DEV, TEST1, STAGE, PROD, and HotFix.
ALM is managed using Azure DevOps.
We have pipelines for building from DEV and HotFix environments.
We have separate release pipelines for Update and Upgrade.

Our Current Workflow:

Development is done in the DEV environment. A build from this environment is created on the TestRelease branch (which originates from main).
The build is then deployed via the release pipeline to the TEST1 environment.
After successful testing, we merge the TestRelease branch into main.
The main branch build is deployed to PROD.
We have a HotFix environment, which is a copy of the DEV environment taken after deployment to PROD (our "gold copy" of the environment).
- In case of a critical issue in PROD, and if the DEV environment is already being used for new feature development, we use HotFix.
- Fixes are made in HotFix and deployed to STAGE for testing (since TEST1 is already occupied with feature testing).

Challenges in Our Current Setup:

We must remember to create a copy of the DEV environment after each deployment and ensure no new feature work is done on DEV before the deployment to PROD is complete.
- We attempted to transfer the solution from the repo to HotFix, but the unmanaged solution only performs updates, not upgrades.
- We need to ensure that the solution in HotFix matches the repository exactly.
Merging the HotFix branch (which originates from the HotFix environment rather than DEV) includes many changes that were not made by developers (e.g., version increments, environment-specific modifications).
- This makes it difficult to analyze what has actually changed in the solution.
Merging a Feature branch will cause the same issue as in point 2.