Software Configuration Management

SpiraTeam allows you to have a single, unified view of your various source code repositories in an easy-to-use web user interface. In addition you can link commits/check-ins in the SCM tool to artifacts in SpiraTeam to provide code-level traceability of changes. The repositories supported include: Subversion, CVS, VSS and Microsoft Team System.

Git


Git is a free & open source, distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Every Git clone is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server. Branching and merging are fast and easy to do.

The SpiraTeam plugin for Git allows you to link your SpiraTeam projects to Git repositories. Once the repositories are linked you can then browse the Git source code repository through the SpiraTeam interface, viewing folders, files and revisions from the convenience of your web browser.

In addition, when team members commit revisions into the Git repository, they can tag the revisions with SpiraTeam artifact tokens which will link the revisions to the appropriate requirement, task or incident in SpiraTeam. These associations can be viewed from within SpiraTeam giving the project manager complete traceability from requirements and incidents through to the corresponding source code changes.

Note: This integration requires at least version 3.0 of SpiraTeam.

Subversion


Subversion is an open-source Software Configuration Management (SCM) system that enables users to work on code simultaneously while preserving previous versions by avoiding collisions in code edits. Developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation.

The SpiraTeam plugin for Subversion allows you to link your SpiraTeam projects to Subversion repositories. Once the repositories are linked you can then browse the Subversion source code repository through the SpiraTeam interface, viewing folders, files and revisions from the convenience of your web browser.

In addition, when team members commit revisions into the Subversion repository, they can tag the revisions with SpiraTeam artifact tokens which will link the revisions to the appropriate requirement, task or incident in SpiraTeam. These associations can be viewed from within SpiraTeam giving the project manager complete traceability from requirements and incidents through to the corresponding source code changes.

Note: This integration requires at least version 3.0 of SpiraTeam.

Mercurial (Hg)


Mercurial is a free, distributed source control management tool. It offers you the power to efficiently handle projects of any size while using an intuitive interface. It is easy to use and hard to break, making it ideal for anyone working with versioned files.

Traditional version control systems such as Subversion are typical client-server architectures with a central server to store the revisions of a project. In contrast, Mercurial is truly distributed, giving each developer a local copy of the entire development history. This way it works independent of network access or a central server. Committing, branching and merging are fast and cheap.

The SpiraTeam plugin for Mercurial allows you to link your SpiraTeam projects to Mercurial repositories. Once the repositories are linked you can then browse the Mercurial source code repository through the SpiraTeam interface, viewing folders, files and revisions from the convenience of your web browser.

In addition, when team members commit revisions into the Mercurial repository, they can tag the revisions with SpiraTeam artifact tokens which will link the revisions to the appropriate requirement, task or incident in SpiraTeam. These associations can be viewed from within SpiraTeam giving the project manager complete traceability from requirements and incidents through to the corresponding source code changes.

Note: This integration requires at least version 3.0 of SpiraTeam.

Concurrent Versioning System (CVS)


The Concurrent Versions System (CVS), also known as the Concurrent Versioning System, is a client-server free software revision control system in the field of software development. Version control system software keeps track of all work and all changes in a set of files, and allows several developers (potentially widely separated in space and/or time) to collaborate.

The SpiraTeam plugin for CVS allows you to link your SpiraTeam projects to CVS repositories. Once the repositories are linked you can then browse the CVS source code repository through the SpiraTeam interface, viewing folders, files and revisions from the convenience of your web browser.

In addition, when team members commit revisions into the CVS repository, they can tag the revisions with SpiraTeam artifact tokens which will link the revisions to the appropriate requirement, task or incident in SpiraTeam. These associations can be viewed from within SpiraTeam giving the project manager complete traceability from requirements and incidents through to the corresponding source code changes.

Note: This integration requires at least version 3.0 of SpiraTeam.

Microsoft Team Foundation Server (TFS)


Team Foundation Server (commonly abbreviated to TFS) is a Microsoft product offering source control, data collection, reporting, and project tracking, and is intended for collaborative software development projects. It is available either as stand-alone software, or as the server side back end platform for Visual Studio Team System (VSTS).

The SpiraTeam plugin for TFS allows you to link your SpiraTeam projects to TFS repositories. Once the repositories are linked you can then browse the TFS source code repository through the SpiraTeam interface, viewing folders, files and changesets from the convenience of your web browser.

In addition, when team members commit changesets into the TFS repository, they can tag the changesets with SpiraTeam artifact tokens which will link the changesets to the appropriate requirement, task or incident in SpiraTeam. These associations can be viewed from within SpiraTeam giving the project manager complete traceability from requirements and incidents through to the corresponding source code changes.

Note: This integration requires at least version 3.0 of SpiraTeam and TFS 2008 or 2010.

Perforce


Perforce is a commercial Software Configuration Management (SCM) system that enables users to work on code simultaneously while preserving previous versions by avoiding collisions in code edits. Developers use Perforce to maintain current and historical versions of files such as source code, web pages, and documentation.

The SpiraTeam plugin for Perforce allows you to link your SpiraTeam projects to Perforce depots. Once the depots are linked you can then browse the Perforce source code depot through the SpiraTeam interface, viewing folders, files and changesets from the convenience of your web browser.

In addition, when team members commit changesets into the Perforce depot, they can tag the changesets with SpiraTeam artifact tokens which will link the changesets to the appropriate requirement, task or incident in SpiraTeam. These associations can be viewed from within SpiraTeam giving the project manager complete traceability from requirements and incidents through to the corresponding source code changes.

Note: This integration requires at least version 3.0 of SpiraTeam and version 4.0 of Perforce.

Microsoft Visual SourceSafe (VSS)


Microsoft Visual SourceSafe (VSS) is a source control software package oriented towards small software development projects. Like most source control systems, SourceSafe creates a virtual library of computer files. While most commonly used for source code, SourceSafe can actually handle any type of file in its database.

The SpiraTeam plugin for VSS allows you to link your SpiraTeam projects to VSS repositories. Once the repositories are linked you can then browse the VSS source code repository through the SpiraTeam interface, viewing folders, files and revisions from the convenience of your web browser.

In addition, when team members commit revisions into the VSS repository, they can tag the revisions with SpiraTeam artifact tokens which will link the revisions to the appropriate requirement, task or incident in SpiraTeam. These associations can be viewed from within SpiraTeam giving the project manager complete traceability from requirements and incidents through to the corresponding source code changes.

Note: This integration requires at least version 3.0 of SpiraTeam and version 6.0 of VSS.

Try SpiraTeam free for 30 days, no credit cards, no contracts

Start My Free Trial

And if you have any questions, please email or call us at +1 (202) 558-6885