Open seandenigris opened 6 years ago
Here's the kickoff quote from Sean's mailling list post:
IIUC you're suggesting that there would be a hook so that I could handle seansprivategitlab:// however I wanted behind the scenes. That sounds intriguing, but how would I ensure that the seansprivategitlab:// support was loaded in the image to be used by MetaC? Also, when you say that cloning isn't necessary, last I checked SSH keys, gitlab, and bitbucket did not seem well-supported by MetaC, so I'm not sure how I would avoid it (or whether I want to; I still don't like the idea of unencrypted credentials in the image, even if they're secure on disk; finally I've been using SmalltalkCI - primarily because I thought Travis was GH-only).
I don't know how to implement, or how/if it fits into MetaC, but sample logic that would seem to cover both or my use cases (remote CI and local dev) is:
@seandenigris doesn't iceberg create local clones using SSH key auth?
@seandenigris it does look like iceberg has come to your rescue unless I am missing something else?
See ML thread. This affects Issues #367 and #474 as well.