Choose source control label as a version of a data source
Today, SQL Compare allows for two options when selecting a version of a source control data source - latest (head), or any other change set. It would be great if there was a third option: to select a version by label. We use labels as a means for controling which code is promoted from development to test to production. Anything ready to promote is labeled as “build ready.” It would be great to use this build ready label when selecting the version from the repository.
Ed
shared this idea
-
Mark.Moore
commented
It's been 5+ years since this has been asked for. I can't believe there is no response from Redgate about this improvement. Labeling our code is an important part of our process. It allows us to branch for hot fixes, compare at a release, etc. Having to go look up where we labeled, get the date/time and then come back in to redgates history viewer and pick the correct item has already show it's a problem as it can cause mistakes.
-
Anonymous
commented
This would vastly improve managing code: to allow developers to continue to check in code to our source management tool that is "in progress", Then developers could select/identify prior versions of code revisions ready to be packaged/promoted; doing so with a label. The challenge now is we cannot "exclude" such in progress revisions for certain objects and leverage a prior changeset id while others are at a higher changeset id level.
-
Anonymous
commented
Adding Version Options will be nice to have. More options are always good
-
Anonymous
commented
This will be a great benefit to our deployment process