cloning submodules
dmamalis opened this issue · 5 comments
Hi there,
I have a git main project (node server) which contains a submodule (public folder containing html, css etc). The hook to the main repository works perfect. It clones the project and starts running the node server. What I need is to hook the submodule so that when changes to the submodules are pushed, Strider will clone the submodules and refresh the project without having to restart the server.
Currently I have two projects on my strider configuration ("server" and "public"). Can strider do that or should I restructure my git repositories?
Greetings!
"starts running the node server"? Is this done in a deploy script or something? I'm not sure I understand your configuration.
No deploy script. The "server" project works with the default configuration for node. It automaticaly deploys (clones, installs npm modules, tests, runs).
Ok, here is some more info.
My git project has a submodule. The command that strider uses to clone everything works when I input it on the command line, so it doesn't look like it's an ssh problem. I removed strider and all its files, dropped its database, reinstalled globally and readded the project. However I still get the same error.
Deployment fails at the prepare stage:
$ git clone --recursive git@bitbucket.com:xxxxx/xxxxxxx . -b develop
Cloning into '.' ...
Submodule 'xxxxxx/xxxxx' (git@bitbucket.org:xxxxx/xxxx.git) registered for path 'xxxxx/xxxxx'
Cloning into 'xxxxx/xxxxx'...
conq: repository access denied. deployment key is not associated with the requested repository.
fatal: could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Clone of 'git@bitbucket.org:xxxx/xxx.git' into submodule path 'xxxxx/xxxxx' failed
$ An unexpected error occured while executing this job. Please report at https://github.com/Strider-CD/strider/issues
Git clone failed with code 500
As I read in #14 (comment) you don't grab the ssh keys from the system. I added them manually on the branch menu but the problem insists. I even exported the keys to STRIDER_SSH_PUB and STRIDER_SSH_PRIV and restarted strider. Still no hope.
Any ideas would be highly appreciated.
It turns out it was a mess on the ssh keys on the strider side. It looks like each branch had different keys which I was not expecting.
I regenerated keys and put them in both the repositories and problem solved.
Thanx anyways.
Keep up the good work