Workaround for private BitBucket repositories

[mdhender]

I ran into issues with dep and a private bitbucket instance. Dep generated errors along the lines of

unable to deduce repository and source type

I found a similar incident. #1551 (closed and linked to #860) had a comment from Sam ("bitbucket doesn't implement go-get metadata correctly") that led me to a workaround.

We set up a vanity server that returns the expected format for bitbucket repos. After updating our import statements (which was easy because they all pointed to that private instance), Dep's working as expected.

[RobvH]

"that returns the expected format for bitbucket repo"

Do you mind share specifically what you did to your vanity repo to accomplish this?

[mdhender]

Our Bitbucket server was prefixing the metadata with /scm/and not adding .git as a suffix. The vanity hack sets them before redirecting to Bitbucket.

You can find the server at https://github.com/mdhender/vango. It's just a light wrapper around Kare Nuorteva's vanity package. The only significant change was adding a response to remind our developers to update their .gitconfig and .ssh. The .ssh change is needed only if the Bitbucket repo's not public (most of our internal repos are private and require an SSH key).

[kevinburke]

Thanks for this! Be sure to try out tip which I think may offer more help here - @theckman added custom Bitbucket logic to try to distinguish these cases.

[mvdan]

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!