Echoing what I think others are saying, would love to see a solution where if we have a binary that matches the SemVersion either remote or local, and it is built then we could use that, otherwise if we have the source it would see that it does not have the right version prebuilt and build that version. If we have it cached we don't pay the cost of building it. If there was no SemVersion associated, like a branch, or in edit mode, then it would require building every time but once it is locked down under a SemVersion then it can be thought of as a version of the code that can be cached. This would be a big time saver only building the code under active revision.