Initiate comparison from package.xml
I'd like to be able to drop a package.xml file on the New comparison screen. Doing that will have two effects.
First off, it will drive the selection of which metadata types to include in the comparison.
Secondly, it will automatically select the components listed in the package.xml on the comparison results page.
This provides a really good way to expediting a deployment, since package.xml are used pretty universally by both IDEs and standard deployment tools (including packages).It also helps me take advantage of the intelligence of automatic dependency and all of the other goodies that Gearset has. Basically I don't want to hear myself say -- well it's probably faster just to deploy via the Migration tool, since I already have a package.
Anonymous
shared this idea
-
Donna
commented
Is the feature you are looking for available when selecting Local Files? Filter comparison by package.xml?
-
Anonymous
commented
A feature where we can upload our own custom package.xml, where system should pick the metadata for extract & compare and deploy based on the package.xml.
-
Gnanasekaran Thoppae
commented
This is a useful feature to combine a hand crafted package list (from git diff for ex.) at the end of a sprint and deploy only those components that were changed (modified/added/delete) instead of hand picking the components from the start.
-
Matt
commented
Agreed: Use case - I need to deploy only a subset of specific items (e.g. documents) to a newly refreshed sandbox.