Submodule HTTP Error 301
Hi!
Recently our Git server changed from HTTP to HTTPS transport. After updating the configurations, TeamCity 2019.1.4 can fetch the branches without any problem. But, when it tries to fetch the submodules, it reads the (old) address from .gitmodule file. Our clients can follow the 301 (Moved permanently) error and do the operation following the new address without changing the .gitmodule files. Teamcity isn't capable of doing this, and it cannot work the branches.
I've asked my team to change the .gitmodule files, but they are concerned about old branches that are not updated, and if some services need to be done, their .gitmodule will be the old one.
Is there something I can do to tell Teamcity to follow the 301 error? Thank you!
Alberto
Please sign in to leave a comment.
Hi, TeamCity server uses JGit library to fetch repos. For TeamCity 2019.1.x it's JGit version 3.7 which unfortunately doesn't support redirects. They added the fix in the later JGit versions. So in your case updating to the forthcoming TeamCity 2019.2 (where we'll bundle JGit 5.4) should fix the issue. Sorry for inconvenience.
Thanks! I thought it was something about JGit. That's a good thing to hear about the update, no need to be sorry, as old branches will be seldom used.
Thank you, we'll update as soon it will be possible.
Cheers
Alberto