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
In some cases it is convenient to store tests in the same Git repository where source code of an application under test is located. For example, if you are using Visual Studio Team Services. From this article you will learn how to execute Rapise tests stored in a Git repository with SpiraTeam and leverage the power of SpiraTeam reporting and analysis features.
This article is obsolete. There is much simpler approach with use of RapiseLauncher Extension for Azure DevOps.
We have been asked several times by customers - how do they migrate an existing Git repository to TaraVault (either self-hosted or hosted by another provider)? This article explains the process.
If you are a cloud SpiraTeam or SpiraPlan user and have been using TaraVault Git repositories, you may find that your existing repositories don't appear in Spira after the update to v6.7. This may be caused by an authentication issue that is easy to fix
When you use SpiraTest with GitLab, the synchronization plugin synchronizes some fields unidirectionally and other fields bidirectionally. To clarify the details, this article illustrates which fields are synched and in which directions.
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.
If you want to migrate your TaraVault Subversion repositories from Subversion (SVN) to Git, to take advanced of the superior merging and branching functionality, as well enabling your teams to work in a distributed manner, this KB article explains the steps to perform the migration, whilst keeping your commit history and branches.
git fetch