Sean Cuevo
My feedback
3 results found
-
6 votes
An error occurred while saving the comment -
4 votes
An error occurred while saving the comment Another use case is a comparison between our main branch and our production org so that we can be notified if they are out of sync. We can do this with a Validation CI job, but that also attempts a deployment validation, which we don't want since it potentially stages a deployment for us.
-
9 votes
An error occurred while saving the comment Yes, even just being able to export this would be beneficial to our teams so that we can easily check what is and isn't being tracked.
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