Prevent Accidental Backing Out of Deployment components when Deploying Multiple Packages
Sometimes I have multiple packages that have been validated, that I am looking to deploy. If they happen to overlap components, then deploying in the wrong order could back out a change made by the earlier deployment.
From this I came up with two ideas that could help:
1) The ability to select multiple validated packages or draft deployments, and click a button that will tell me if they have overlapping components. That will let me know if I have anything to worry about; if they overlap then maybe I should combine them into one package.
2) The ability to compare a gearset validated package with the source to see if any of the components in it have changed in the source since the validation was done. This will let me know if I may end up backing out stuff. There are cases where it is okay if there are differences, like a developer has moved on to make additional changes that aren't supposed to be in the deployment, but it could also denote an issue where it's an old validation that could back out stuff that was deployed in other packages. I know it is possible to click "View Comparison", then click "Rerun Comparison", and then manually compare those results to the results that selecting "View Comparison" showed, but doing that is cumbersome, and this way would be a faster compare that potentially could off a special filter that will only include the metadata types that were selected in the package.