Allow for Scheduled Comparisons
Like Monitoring Jobs, allow users to choose a source, target, and metadata filter, and schedule when a comparison runs.
The primary goal of this would be time savings. To have that data already retrieved and cached so you can go in, make your selections, and move toward deployment more quickly. Possible applications include recurring deployments, planning out your workday, etc. This addition would be for non-Integration users.
Brett Carr
shared this idea
-
Ken Roberts
commented
Agreed. I like to compare my sandboxes (dev -> staging -> production) before working on something new. It would be a great timesaver to refer to nightly scheduled comparisons before starting work versus having to manually step through each comparison and wait for the results.
-
Sean Cuevo commented
This feature is really necessary because regardless of process controls sometimes changes happen in Production without going through version control. I need to know if these changes happen and our repo is out sync in order to re-sync the repo and production so that we don't accidentally overwrite something in production with out of date repo metadata.
Currently we have a scheduled validation only job that sends a notification on completion so we can see if there are any changed objects. However, Gearset of course considers this a successful deployment. Even if I could change that notification the only send one if there are changes to be deployed, that would be immensely more helpful
-
Molly
commented
This would be great!