List of Pages I’ve already read, referenced and tried to use: Travis build failed due to git submodule repository not found I have the Clone or Import setting flagged on for both repos relative to the suggestion in the link below so I don’t think it is a permission issue on the travis interface side: So basically from what I am seeing is the git submodule command is not recognizing the key access. Set the same ssh travis key to each repo independently, once again for each independent repo it was able to clone but when attempting to clone the sub module the above error occurred.Set the ssh travis key to full account access allowing access to all repositories under the umbrella, for each independent repo it was able to clone but when attempting to clone the sub module the above error occurred. With that key I attempted each of the following steps. I know the key works for the sub_mod_repo because I have a separate build for it that works fine when it is the “main repo.” Originally both were utilizing the default key travis generates and links for each repository but I updated it with a custom travis specific key. Retry scheduledīoth these repositories have ssh key access through the same key. Submodule 'repo' () registered for path 'sub_mod_repo'Ĭloning into '/home/travis/build/repo_org/main_repo/sub_mod_repo'.įatal: clone of '' into submodule path '/home/travis/build/repo_org/main_repo/sub_mod_repo' failedįailed to clone 'sub_mod_repo'. On clone failure the output message is: $ git submodule update -init -recursive The submodule is owned under the same umbrella of the main repository and both are private. My build is failing on: $ git submodule update -init -recursive Hi guys, hoping to get some feedback to see if I’m missing something with my build.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |