Perhaps this complicated my situation, but if you see me use command x, instead of command Y, this might be why. Just to preface, I'm stuck using git 1.7.1 on my staging server, which as near as I can tell was released early 2011, so just a few years old now. If you're using Github, you might be interested i n this answer too. Some of this may apply to other services as well, though I've only been tested it with Bitbucket. So I'm documenting the steps I took to make this work with Bitbucket. There are some good source out in the interwebs on this already, but they don't directly address private submodules. I needed to create a deployment strategy for wordpress that employed private submodules repos.
#Bitbucket create submodule how to
How to use public & private submodules within a repo I've even tried absorbing the user name into the alias like so Host :īut this results in conq: invalid repository syntax.Īt this point I can't see the forest, never mind trees. While this looks promising, the result is the same ssh: Could not resolve hostname. *A list of all the repos associated with that key* This deploy key has read access to the following repositories: Now when I test it with ssh -Tv after a lot of output, we get: authenticated via a deploy key. On the server, the alias for points to this common key. My last approach has been to make one common key (different from my account key, they wont let you do that) and assign it to the parent repo, and each submodule. But this simply isn't working, the parent key is being recognised, but aliases for submodules keys are not. Thus far i've been hunting for ways to reference these aliased-keys in. When that didn't work for subs, I set up keys for each of them, and then on the server, aliases for each of them too, but keeping the parent repo key the same as before.
My approach so far has been to create an ssh key alias linking to the parent key that I established for this server in my personal bitbucket settings. I would have thought the error would have read ssh: Could not resolve hostname *:username* -HUMMMM The result was the same error: ssh: Could not resolve hostname :username. There must be some caching in effect, because changing the host on the alias to something impossible like. Obviously the alias isn't resolving at all.Īs option 1 seemed to be at least making the ssh request, I manipulated the ssh alias that I thought was routing the request to the proper key. Result: ssh: Could not resolve hostname :username It looks like an alias is resolving, but something is blocking the key? So sadly this operation does not seem to address issues with missing private repos.
None of the private repos will be listed in this operation.
#Bitbucket create submodule update
After each change, Im running: git submodule update -init -recursiveĮDIT: as suggested in comments re updating the links, at this point a git submodule sync will sync all submodules which have already completed a pull. This deploy key has read access to the following repositories: XXXXX
You can use git or hg to connect to Bitbucket. Just to be sure the aliases are working we can test them with: ssh -Tv when successful returns a lot of output ending with. So after making individual (I could have created just one) keys and creating ssh aliases for each of them (on the staging server), I'm stuck as to how to reference those key properly. (scroll down to 'Private repos" heading for some interesting comments in this article by Luke Woodward) This isn't totally surprising as to access private repos, we need to associate another key, which cannot be the same as the one associated with the account. Here is where things go wrong and ssh can't connect and the process halts on the first private repo. # git fetch -recurse-submodules=yes # introduced 1.7.3 Git submodule foreach git pull origin master # git submodule update -remote # Not available in 1.7.1 So far so good but the submodules are empty: # Update submodules The staging server has a few locked files in the environment which I have to work around, so I am initialising as follows: git init This is working as the private parent repo is pulling in just fine. Ssh: Could not resolve hostname :username: Name or service not known, and the process stops here.Īs per the docs, I have set up a deployment key for the staging server and have created an ~/.ssh/config alias to point to that key. However the first private repo encountered returns this The submodules which are not private are coming in without issue. I have a private repo with several submodules, some of which are also private. Git version 1.7.1 ( I have no power over this, on this server )
0 kommentar(er)
