You’re offline. This is a read only version of the page.
Hi,
Can you please help in clarifying the following scenarios given by a partner:
1. Changeset based code merge from Dev to Test environment :
When we do this, we run into dependency problems specially when the number of changesets are large & dependencies are not very easily visible. There is a cherry pick capability which is available if we use Git as source control, which we cannot since all build/release pipelines supports only TFVC source control. So we don’t have really have a choice there. Here is a comparison of https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/comparison-git-tfvc git vs tfvc but we can use only with tfvc for now.
So the question is how can we reliably do this “changeset based code merge”? Are there any tools to support & ensure that dependencies can be mapped/managed without any problems. We used to do this before but ran into manual dependencies (and hence injected bugs). Then I recommended to stop using this.
2. There is no way to properly handle the last moment code rollback, except having the correct amount of time between the Signoff & Cut-off for production deployment
Is there any option to help with this roll back scenario?
3. How can we use two branches mapped to single machine for a developer for Dynamics 365 Fin & Ops, as Visual studio allows developer to have only one mapping for one folder (Metadata to Packages)?
Any input on this will be very helpful
1) What kind of dependencies are you talking about?
2) Can you please explain your current process and the problem you have with? Just saying that you can't handle it properly isn't very detailed.
3) You have several options: use multiple developer VMs, remap the single packages folder as needed or use two Packages folder (each mapped to a single branch) and switch between them. But first, ask yourself which branches allow development and have a process for merging between them.
Share
Report
All responses (
Answers (
237,965
