If you want to migrate a Subversion repositories from Subversion (SVN) to Git follow the steps below to keep your commit history and branches.
Migrating to Git provides a number of significant benefits like superior merging and branching, as well enabling teams to work in a distributed manner.
When you integrate SpiraTeam or SpiraPlan installed on-premise with an external Git source code repository, Spira has to maintain a copy of the Git repository locally. Sometimes you need to refresh this Git repo manually if an update did not complete. This article explains the process
When you use the Perforce Provider for Spira you may sometimes run into a Windows folder permission error. This is due to the Perforce API running as a specific user that does not have access to the Windows temporary profile storage area.
When SpiraTeam or SpiraPlan is connecting to a Subversion (SVN) repository running on Windows Server, sometimes the Windows server will not close connections fast enough, causing the cache build to fail.
If you are using SpiraTeam and SpiraPlan on-premise, and are looking at our TaraVault cloud-hosted code management service, this article explains what TaraVault is, and how you can have the same functionality on Premise.