Home

SpiraPlan/Team Version Control Integration Guide

1. lt cvs repository url gt cvsroot lt repository path gt For example sharpcevslib cvs sourceforge net cvsroot sharpcvslib o Login Password The user id and the password of the user to use while accessing and retrieving information from the CVS server If you are accessing a public repository anonymously just use anonymous for both username and password and it will be handled correctly o Custom 01 This must contain the name of the connection protocol being used to access the CVS server The following protocols are supported pserver the first access protocol according to the client server scheme the most simple and the fastest one Its imperfection it transfers all the data unsecured If you need to secure codes and user passwords do not use this protocol in public nets ext or ssh access protocol using SSH Secure Shell It is used for accessing UNIX servers and it supports all data encodings sspi access protocol for Windows server with data encoding support o Custom 02 This must contain the name of the module you wish to access in the CVS repository e When finished click the Insert button and you will be taken back to the Version Control integration list page with CvsProvider listed as an available plug in e Verify that you are in the correct project using the drop down at top and click on the Project Settings link for the CvsProvider You will get a screen listing all th
2. e Log in as the Administrator and go into SpiraTeam main Administration page and click on the Version Control link under System e Click the Add button to enter the Plug in details page The fields required are as follows st External Projects v gt Sample Application Two Planning Testing Tracking y Reporting Administration gt Version Control amp Projects View Edit Projects s Edit Project Groups s Planning Options Please enter edit the following information for the provider The exact information that needs to be entered is specific to each provider and you should refer to the documentation for the provider when entering changing it Edit Provider GitProvider lt lt Back to Version Control Home s Project History Changes al Data Tools Name GitProvider amp Users View Edit Users Description Pa s Project Membership s Active Sessions e v Active Pending Requests View Edit Roles Default Settings amp Incidents The following settings are used for any projects that do not define their own settings Edit Types Connection git github com libgit2 libgit2sharp git Edit Statuses aa Edit Priorities Login anonymous Edit Severities Password S Edit Workflows Domai amp Notifications Custom 01 Email Configuration Custom 02 Notification Events Custom 03 k Notification Templates Custom 04 am
3. P4A PI dll o P4DN dlil o PerforceProvider dll e Log in as the Administrator and go into SpiraTeam main Administration page and click on the Version Control link under System e Click the Add button to enter the Plug in details page The fields required are as follows Edit Provider PerforceProvider Name PerforceProvider Description For connecting to the perforce Server Active Default Settings The following settings are used for any projects that do not define their own settings Connection public perforce com 1666 Info Login uest Password Peers Domain Custom 01 PerforceProvider Custom 02 i public Custom 03 Custom 04 Custom 05 o Name The name must be PerforceProvider o Description The description is for your use only and does not affect operation of the plug in o Active If checked the plug in is active and able to be used for any project o Connection Info This field is the server s DNS or IP with the port to connect to No depot information or root directory is to be specified here Do not enter in any protocol like http orftp O Login Password The user id and the password of the user to use while accessing and retrieving information from the Subversion server If either field needs to be blank enter in anonymous Domain Not used Custom01 The client name is to be entered here The plugin will attempt to create the client if it doe
4. 5 Integrating with VSS Visual SourceSafe VSS from Microsoft is a Software Configuration Management SCM system that enables users to work on code simultaneously while preserving previous versions by avoiding collisions in code edits This plug in will allow users of SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam to be able to browse a VSS database and view revisions linked to SpiraTeam artifacts While users working on the code will usually have a complete copy of the repository on their local systems this plug in will access the VSS database remotely The rest of this section outlines how to install and use the plug in with SpiraTeam Note The plug in will allow users to download and view different revisions of files and view revision logs but no changes to the repository are allowed through the plug in 5 1 Installing the VSS Plug In To install the VSS Version Control plug in follow these steps e Install a copy of Visual SourceSafe on the same server that is running SpiraTeam if it is already installed on the server you can disregard this step e Copy the following files from the plug in zip archive into the VersionControl sub folder of the SpiraTeam installation o VssProvider dll o SourceSafe Interop dll e Log in as the Administrator and go into SpiraTeam main Administration page and click on the Version Control link under System e Click the Add button to enter the Plug in details page
5. My Profile Administration Log Out Help e spiraTeam ee My Page Project Home Planning Testing Tracking Reporting Incidents Tasks Resources Source Code Role Project Owner Repository Browser Refesh HelloWorld gt Refresh Apgly Fiter Clear Fites aemp SamSSTesfarcosfs in OV FileNameAY Size AY Author AY Latest Revision AY LastEdited AV hima LS B src 2 default build 0KB Admin 3 Feb 2010 B Tools 2 HelloWorld cs 0 KB Admin 3 Feb 2010 B nant 0 85 rc3 B HelloWorid js 0 KB Admin 3 Feb 2010 Bbi a HelloWorld vb 0 KB Admin 3 Feb 2010 a E doc amp examples Show fis Y rows per page i4 lt Displaying page 1 fof 1 gt b schema amp nantcontrib 0 85 1c3 B Nunit2Repon 1 2 3 The folder tree of the repository is on the left and files in the current selected directory will be listed in the right table Note that this view will always show the most recent revision of the database The file view will display the filename the current revision number of the file and the date of the last check in You can filter and sort on any of the columns as well 5 2 2 Viewing File Details To view the file details click on a file in the right hand side of the repository The file details page displays the details on the selected revision By default it will be the most recent revision unless you clicked to view the file details from a revision By clicking on the file name you can dow
6. Settings link for the GitProvider You will get a screen listing all the same configuration settings GitProvider Project Settings Sample Application Two Change Project lt lt Back to Version Control Home Please edit the following project specific settings for the GitProvider version control provider If you leave any fields blank then the value will be taken from the provider s default settings To stop using this provider on the project just set the Active flag to No below Project Name Sample Application Two Active for Project Yes v Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 o Be sure to change the Active field to Yes or the repository will not be available for the current project o Any other settings entered on this page will override and have the same use as the general settings that you created above You would use these settings if you will have more than one project access different code repositories e Initial setup is complete click on the Source Code menu under the Tracking tab to navigate and browse the source code repository 8 2 Using Git with SpiraTeam While being able to browse the source code repository can be useful in itself the real strength comes from linking artifacts in SpiraTeam including Incidents Requirements and Tasks to revisions checked into the software repository 8 2 1 Viewing the Repository Tree View the source code tree by selecting th
7. and there is an error either on the page or in the Application Event Log that says Could not load file or assembly Subversion control and library files come in both 32 bit and 64 bit Win32 or x64 versions If this error occurs it is most likely that the wrong version of the files were installed Download the correct version from the Inflectra website and overwrite the files in the VersionConirol folder e SpiraTeam reports that the login information is incorrect In this case double check the Version Control settings both for the Project which overrides the general settings and the general settings Project settings will over ride the general settings Be sure to use a user that has access to all nodes in the tree starting from the root repository location e f you are taken back to the repository screen and given a message saying that the requested file was deleted from the system this means that an attempt was made to view details on a file that is no longer part of the HEAD revision This can happen when a file is deleted or renamed and this is a normal condition in the code repository not necessarily an error with Subversion or SpiraTeam 3 Integrating with Perforce 3 1 Installing the Perforce Plug In To install the Perforce Version Control plug in follow these steps e Copy the following files to the folder named VersionControl in the SpiraTeam installation folder o _Inflectra Global dll o
8. 2012 intemals E Phase ina a E merge E E Repository java 11759 KB Jan Sorensen 5f8aa17d6a3 13 Feb 2012 E RepositoryConfiguration java 4032 KB Jan Sorensen 49d6dcfidecd 12 Feb 2012 oa resources 5 site z Dtest WorkingCopy java Show 15 V rows per page 3350 KB Martin Geisler f07864272c4f 11 Feb 2012 4 lt Displaying page S of 1 gt gt View Revision Log The folder tree of the repository is on the left and files in the current selected directory will be listed in the right table Note that this view will always show the current TIP branch of the repository The file view will display the filename the current revision number of the file and the date of the last commit You can filter and sort on any of the columns as well 7 2 2 Viewing File Details To view the file details click on a file in the right hand side of the repository The file details page displays the details on the selected revision By default it will be the TIP branch unless you clicked to view the file details from a revision By clicking on the file name you can download the specified revision of the file to your local machine This does not do a Mercurial clone or pull you are merely downloading the file to your local machine Welcome System Administrator My Profile Administration Log Out Help My Page Project Home Planning Testing Tracking Reporting Tasks Resources Source Code gt File Detail
9. Changed Update Date 2 4 2010 11 16 26 AM Properties Changed E License txt 4 Feb 2010 Show fis Y rows per page lt lt 4 Displaying page a of 1 pi The revision details screen shows the log for the action performed the date and author At the bottom of the page are two tabs Files and Associations The Files tab lists all files that were a part of this revision with their full path latest revision and date of edit The Associations tab shows any artifact Incident Requirement Test Case Test Set that the log message references See section 4 2 4 for information on how to link a revision with a VSS check in or other action Files Associitions 29 Dec 2009 W Cannot log into the application Fred Bloggs Incident INQO005s 29 Dec 2009 j Sample Requirement Fred Bloggs Requirement RQ000028 29 Dec 2009 Sample Test Joe P Smith Test Case TCOO0014 5 2 4 Linking Artifacts Linking an artifact is quite simple To maintain the readability of VSS check in messages we adopted a square bracket token The token is in the format of lt artifact i dentifier gt lt artifact id gt The first half the Artifact Identifier is a two letter code that is used throughout SpiraTeam and is visible on almost every page in the application For example a requirement s identifier is RQ Incidents are IN and test cases are Tc The artifact ID is the number of the artifact So by creating a commit message that r
10. Linking an artifact is quite simple To maintain the readability of TFS check in messages we adopted a square bracket token The token is in the format of lt artifact identifier gt lt artifact id gt The first half the Artifact Identifier is a two letter code that is used throughout SpiraTeam and is visible on almost every page in the application For example a requirement s identifier is RQ Incidents are IN and test cases are Tc The artifact ID is the number of the artifact So by creating a commit message that reads Due to requirement 12 RQ 12 the code for toString in class XMLparser was modified This also fixed Incident 1034 IN 1034 Spiraleam will automatically detect tokens and will include links to them under the Associations tab for a revision detail If you forget to add the association during the commit you can use the Add Association option within Spiraleam to add the association after the fact 6 3 Troubleshooting While integration with TFS is rather sophisticated behind the scenes as a user you will only receive a couple of errors that will prevent the integration from working e Spiraleam will not display the login page and there is an error either on the page or in the Application Event Log that says Could not load file or assembly If this error occurs it is most likely that the TfsProvider dll or some of its dependent assemblies were not correctly placed in the
11. SubversionProvider Project Settings Spiral eam Change Project lt lt Back to Version Control Home Please edit the following project specific settings for the SubversionProvider version control provider If you leave any fields blank then the value will be taken from the provider s default settings To stop using this provider on the project just set the Active flag to No below Project Name SpiraTeam Active for Project ves Connection Info svn i local inflectra com SpiraTeam Login Password o Be sure to change the Active field to Yes or the repository will not be available for the current project o Any other settings entered on this page will override and have the same use as the general settings that you created above You would use these settings if you will have more than one project access different code repositories e Initial setup is complete click on the Source Code menu under the Tracking tab to navigate and browse the source code repository 2 2 Using Subversion with SpiraTeam While being able to browse the source code repository can be useful in itself the real strength comes from linking artifacts in SpiraTeam including Incidents Requirements and Tasks to revisions checked into the software repository 2 2 1 Viewing the Repository Tree View the source code tree by selecting the Source Code link under the Tracking tab You will get a screen similar to Intect
12. The fields required are as follows x i Name VssProvider Description SourceSafe Active Default Settings The following settings are used for any projects that do not define their own settings Connection Info Login Password Domain Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 o Name The name must be VssProvider o Description The description is for your use only and does not affect operation of the plug in o Active If checked the plug in is active and able to be used for any project o Connection Info This field points to the filepath where the srcsafe ini file is located which contains the VSS database information For example c VssDatabases Projectl srcsafe ini o Login Password The user id and the password of the user to use while accessing and retrieving information from the VSS database If the repository doesn t require a password just use anonymous as the password o Domain is not used by the VSS plug in and can be ignored o Custom01 05 are not used by the VSS plug in and can be ignored e When finished click the Insert button and you will be taken back to the Version Control integration list page with VssProvider listed as an available plug in e Verify that you are in the correct project using the drop down at top and click on the Project Settings link for the VssProvider You will get a screen listing all the same configu
13. VersionControl folder of the SpiraTeam installation e SpiraTeam reports that the login information is incorrect In this case double check the Version Control settings both for the Project which overrides the general settings and the general settings Project settings will over ride the general settings Be sure to use a user that has access to all nodes in the tree starting from the root repository location e f you are taken back to the repository screen and given a message saying that the requested file was deleted from the system this means that an attempt was made to view details ona file that was deleted in TFS This is a normal condition in the code repository not necessarily an error with TFS or SpiraTeam 6 4 Enforcing Associations with a Custom Policy As described in section 5 2 4 above you can easily associate check ins of code in TFS with relevant Spiraleam artifacts by adding the appropriate artifact identifier in the commit messages In order to enforce this process one of our customers has written a custom Visual Studio 2008 and 2010 2012 Team System check in policy that will force users to enter at least one Spiraleam artifact in each of the check in comments This policy will also check the IDs of the supplied artifacts to make sure they exist in the appropriate SpiraTeam installation To install the custom check in policy you should download the SpiraPolicySetup msi for 2008 or SpiraPolicy vsix for 2010 install
14. all the Git repositories that have been accessed through SpiraTeam To purge a module just select it and choose the Delete Folder option in Windows Legal Notices This publication is provided as is without warranty of any kind either express or implied including but not limited to the implied warranties of merchantability fitness for a particular purpose or non infringement This publication could include technical inaccuracies or typographical errors Changes are periodically added to the information contained herein these changes will be incorporated in new editions of the publication Inflectra Corporation may make improvements and or changes in the product s and or program s and or service s described in this publication at any time The sections in this guide that discuss internet web security are provided as suggestions and guidelines Internet security is constantly evolving field and our suggestions are no substitute for an up to date understanding of the vulnerabilities inherent in deploying internet or web applications and Inflectra cannot be held liable for any losses due to breaches of security compromise of data or other cyber attacks that may result from following our recommendations SpiraTest SpiraPlan SpiraTeam and Inflectra are registered trademarks of Inflectra Corporation in the United States of America and other countries Microsoft Windows Visual Studio Explorer and Visual SourceSafe are re
15. can filter and sort on any of the columns as well 2 2 2 Viewing File Details To view the file details click on a file in the right hand side of the repository The file details page displays the details on the selected revision By default it will be the HEAD revision unless you clicked to view the file details from a revision By clicking on the file name you can download the specified revision of the file to your local machine This does not do an SVN checkout you are merely downloading the file to your local machine S y Inflectra Products gt Spiraleam Planning Testing Tracking Reporting Source Code gt File Details lt lt Back to File List Current Branch gt Trunk v amp Business ArtifactLinkManager cs ArtifactManager cs Attachment cs File Path svn Nocal inflectra com SpiraTeam Trunk Business ArtifactLinkManager cs Automation cs File Type Size C Source 45 KB BuildManager cs Author mmorrey _ Business csproj Preview Revisions Associations ClassDiagram1 cd E ComponentManager cs using Inflectra SpiraTest Common using Inflectra SpiraTest DataModel CustomPropertyManager cs using System DashboardManager cs using System Collections AD using System Collections Generic DataAccess cs using System Ling 4 DataMapping cs j using System Linq Expressions Di using System Reflection E ESES using System Text RegularExpressions 4 EventManage
16. over ride the general settings Be sure to use a user that has access to all nodes in the tree starting from the root repository location e f you are taken back to the repository screen and given a message saying that the requested file was deleted from the system this means that an attempt was made to view details on a file that is no longer part of the HEAD revision This can happen when a file is deleted or renamed and this is a normal condition in the code repository not necessarily an error with CVS or SpiraTeam 3 4 Data Purging Since the integration with CVS requires that a working copy of the CVS repository be stored on the Spiraleam server you may decide at some point to unlink a disused CVS repository from SpiraTeam to save disk space However unlinking the repository through the SpiraTeam web interface will not remove the working copy of the repository from the server To permanently remove a repository from the SpiraTeam server you need to locate the following path o Windows XP 2003 C Documents and Settings All Users Application Data o Windows 2008 7 Vista C ProgramData If you look inside this folder you will see a subfolder called Inflectra and under that will be a subfolder called CvsProvider If you open up this subfolder you will see a list of all the CVS modules that have been accessed through SpiraTeam To purge a module just select it and choose the Delete Folder option in Windows
17. page 1 aof 1 i The folder tree of the repository is on the left and files in the current selected directory will be listed in the right table The file view will display the filename the current revision number of the file and the date of the last commit You can filter and sort on any of the columns as well The page will display the folders and files for the currently selected branch in the example above master you can change the current branch at any time by selecting it from the dropdown menu master origin Doc Split origin Feature Start Page origin master onidin new installer origin Rapise 7 1 8 2 2 Viewing File Details To view the file details click on a file in the right hand side of the repository The file details page displays the details on the selected revision By default it will be the latest revision in the current branch unless you clicked to view the file details from a revision By clicking on the file name you can download the specified revision of the file to your local machine This does not do a Git clone or pull you are merely downloading the file to your local machine S y Inflectra Products gt Rapise Planning Testing Tracking Reporting a Source Code gt File Details lt lt Back to File List Current Branch gt Master v amp Business app config AutomationEngine cs 6 Launcher Business csproj Launcher Business csproj user Logger cs
18. save disk space However unlinking the repository through the SpiraTeam web interface will not remove the working copy of the repository from the server To permanently remove a repository from the SpiraTeam server you need to locate the following path o Windows XP 2003 C Documents and Settings All Users Application Data o Windows 2008 7 Vista C ProgramData If you look inside this folder you will see a subfolder called Inflectra and under that will be a subfolder called MercurialProvider If you open up this subfolder you will see a list of all the Mercurial repositories that have been accessed through SpiraTeam To purge a module just select it and choose the Delete Folder option in Windows 8 Integrating with Git Git is a Distributed Version Control System DVCS system that keeps track of software revisions and allows many developers to work on a given project without necessarily being connected to a common network since it doesn t rely on a central repository but instead distributes copies of the entire source code repository to each user s workstation The SpiraTeam plug in for Git allows users of SpiraPlan or SpiraTeam hereafter referred to as Spiraleam to be able to browse a Git repository and view revisions linked to SpiraTeam artifacts The plug in will clone a read only bare i e no working folder copy of the Git repository onto the Spiraleam server and use that for displaying the list o
19. the tree starting from the root repository location If you are taken back to the repository screen and given a message saying that the requested file was deleted from the system this means that an attempt was made to view details on a file that is no longer part of the HEAD revision This can happen when a file is deleted or renamed and this is a normal condition in the code repository not necessarily an error with Subversion or SpiraTeam Any other errors about not being able to load the version control provider will have the error messages logged in the web server s that hosts SpiraTeam Application Event Log When conotacting support be sure to have the event logs ready 4 Integrating with CVS The Concurrent Versions System CVS is a Software Configuration Management SCM system that enables users to work on code simultaneously while preserving previous versions by avoiding collisions in code edits This plug in will allow users of SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam to be able to browse a CVS repository and view revisions linked to SpiraTeam artifacts The plug in will download a working copy of the CVS repository onto the SpiraTeam server and use that for displaying the list of files folders The list of revisions will be queries dynamically from the CVS repository on an as needed basis The rest of this section outlines how to install and use the plug in with SpiraTeam Note The plug in will allow use
20. 1 20 22 PM Latest Revision 26375 gt Refresh Apply Filter Clear Filter asandman mmorrey mmorrey asandman asandman Commit Date AV Added branch list to source code file list page 14 Aug 2014 16 Jun 2014 23 May 2013 29 Apr 2013 21 Dec 2012 Small code fixes that won t break tests Removed re throwing exceptions and fixed two issu Added UTC code Fix bug that prevented comments to be edited in th asandman 2 2 3 Revision Details 22 Oct 2012 Yes Yes Yes Yes Yes Yes By clicking on a revision in SpiraTeam you will be taken to the revision details page 2 System Administrator v Inflectra Products gt Spiraleam Planning Testing Tracking Reporting r Sh ed lt lt Back to Revision List v ArtifactLinkManager cs 26555 26067 426046 4 26038 26029 Source Code gt Revision Details Current Branch fe Trunk v Source Code Revision 4126555 Notes Partial Fixes to DataTools Edited By Build 5 SpiraTeam Trunk 398 Last Edited 9 8 2014 8 50 04 PM mmorrey Files Associations Content A Any V v No No No No No No Yes Properties A No gt Refresh Apply Filter Clear Filter 11 KB 24 KB 34 KB 5 KB 10 KB 17 KB 45 KB 8 KB 12 KB ArtifactAttachmentView cs asandman ArtifactCustomProperty cs E AntifactField cs 4 ArtifactFieldDisplay cs 4 ArtifactFieldType cs AntifactLink cs asandman a
21. 9 KB dmarkovtsev 900ab7ec0e Modified 10 Oct 2014 o SpiraConnect cs 34100 KB dmarkovtsev 900ab7ec0e Modified 10 Oct 2014 Show 15 rows per page M lt 4 Displaying page 1 Fa of 1 gt Pi The revision details screen shows the log for the commit the commit date and author At the bottom of the page are two tabs Files and Associations The Files tab lists all files that were a part of this commit with their full path size latest revision and date of edit The Associations tab shows any artifact Incident Requirement Test Case Test Set that the log message references See section 8 2 4 for information on how to link a revision with a Git commit Source Code Revision 4 5bfb75478c Notes Fixes IN 002943 Edited By Adam Sandman ContentA Yes Build F Rapise Master 208 Properties A Yes Last Edited 10 1 2014 12 07 38 PM Files Associations 1 Oct 2014 W RapiseLauncher doesn t execute on our internal ser Adam Sandman Fixes IN 002943 Incident INO02943 gt Add Association 8 2 4 Linking Artifacts Linking an artifact is quite simple To maintain the readability of Git commit messages we adopted a square bracket token The token is in the format of lt artifact identifier gt lt artifact id gt The first half the Artifact Identifier is a two letter code that is used throughout SpiraTeam and is visible on almost every page in the application For example a requirement s identifier i
22. PauseTimer cs Preview Revisions PendingSet cs Rapise cs 1 using System i using System Collections Generic RapiseSettings cs 3 using System Text RunTestThread cs using System Diagnostics StringExtensions cs er pn ern ea TestResult cs TestSetLaunch cs Source Code File AutomationEngine cs File Path a2696b980bf38dc63c36cdd5b87692a7247b2f09 File Type Size C Source 18688 KB Last Edited 10 10 2014 3 47 06 PM Author dmarkovtsev Latest Revision 900ab7ec0e using Inflectra Rapise RapiseLauncher Business DataObjects using System Text RegularExpressions namespace Inflectra Rapise RapiseLauncher Business lt summary gt This class is responsible to actually communicating with SmarteStudio Rapise s API for executing the tests and receiving the results lt summary gt public class AutomationEngine lt summary gt Constructor lt summary gt lt param name server gt The server name lt param gt lt param name username gt The username lt param gt lt param name password gt The password lt param gt public AutomationEngine string server string username string password Underneath the file details are tabs that show a preview of the file with syntax highlighting a list of all the revisions that this file belongs in or was committed to who performed the commit and the log message for the commit and a t
23. S te Fumie INFLEC I RA door sanders h 12 Nov 2014 56 Test Prac for TS 5 8 Foon Designer cs INFLECTRA adam sandman 5 12 Nov 2014 BE Propurbs Program cs INFLECTRA adam sandman 12 Nov 2014 i Test Propel for TFS Source cs xH INFLECTRA adam sandman i 12 Nov 2014 s Promdi Test Project for TES Sou TONN VETSCE INFLEC TR Addar sader h 12 Nov 2014 Other Operations Show 15 F rows per page 4 4 Displaying page T of 1 m gt Vasa Aven Li The folder tree of the repository is on the left and files in the current selected directory will be listed in the right table Note that this view will always show the most recent revision of the database The file view will display the filename the current revision number of the file and the date of the last check in You can filter and sort on any of the columns as well The page will display the folders and files for the currently selected branch in the example above Main you can change the current branch at any time by selecting it from the dropdown menu Current Branch the current folder b Main b Test Project for TFS Source b Test Project for TFS Source branchi l 6 2 2 Viewing File Details To view the file details click on a file in the right hand side of the repository The file details page displays the details on the selected revision By default it will be the most recent revision unless you clicked to view the file details from a revision By clicking on the file n
24. Team and the appropriate version control tool For information regarding how to use the Source Code management features of SpiraPlan Team please refer to the SpiraPlan User Manual or the Spiraleam User Manual Each of the sections in this document covers a different version control system so we recommend using the table of contents on the left to locate the version control system you re looking to integrate then read the installation and usage instructions 2 Integrating with Subversion Subversion also known as SVN is a Software Configuration Management SCM system that enables users to work on code simultaneously while preserving previous versions by avoiding collisions in code edits While users working on the code will usually have a complete copy of the repository on their local systems this plug in will access the repository remotely by use of the svn http and https protocols Note that svn ssh may be supported on a server by server basis Due to the methodologies in which IIS handles web requests and runs on the server any SSH connection certificates that have trust issues will be automatically accepted Therefore we recommend using an IP address to connect to the server instead of a DNS name that could be redirected to an unsafe connection The current version of the Subversion plugin requires SpiraPlan or SpiraTeam v4 2 0 2 or later 2 1 Installing the Subversion Plug In To in
25. The exact information that needs to be entered is specific to each provider and you should refer to the documentation for the provider when entering changing it Name TfsProvider Description W Active Default Settings The following settings are used for any projects that do not define their own settings Connection Info http vm tfs 8080 tfs DefaultCollection Login Password Domain INFLECTRA o Name The name must be TfsProvider o Description The description is for your use only and does not affect operation of the plug in o Active If checked the plug in is active and able to be used for any project o Connection Info This field points to the URL used for accessing the Team Foundation Server Typically TFS runs on website port 8080 but you may need to check with your IT administrator to verify The exact connection URL will depend on your version of TFS For TFS 2005 2008 e http myservname 8080 For TFS 2010 e http myservname 8080 tfs projectcollection e Where projectcollection is the name of the project collection you will be connecting to For TFS 2012 or later e http myservname 8080 tfs projectcollection e Where projectcollection is the name of the project collection you will be connecting to o Login Password The user id and the password of the user to use while accessing and retrieving information from the TFS repository If the repository doesn
26. Y LatestRevision AY Action AY Last Edited AY m a eS ee App config 1 KB INFLECTRA adam sandman Undefined 12 Nov 2014 4 Assemblyinfo cs 2 KB INFLECTRA adam sandman Undefined 12 Nov 2014 Form1 cs 1KB INFLECTRA adam sandman Undefined 12 Nov 2014 Form1 Designer cs 2 KB INFLECTRA adam sandman Undefined 12 Nov 2014 a Program cs 1 KB INFLECTRA adam sandman Undefined 12 Nov 2014 Undefined 12 Nov 2014 Undefined 12 Nov 2014 Undefined 12 Nov 2014 Undefined 12 Nov 2014 Resources Designer cs 3 KB INFLECTRA adam sandman Resources resx 6 KB INFLECTRA adam sandman Settings Designer cs 2KB INFLECTRA adam sandman Settings settings 1KB INFLECTRA adam sandman Ion ton Ion ton ten ten len Ion ion OWO O O O O O O O LE E The revision details screen shows the log for the action performed the date and author At the bottom of the page are two tabs Files and Associations The Files tab lists all files that were a part of this revision with their full path latest revision and date of edit The Associations tab shows any artifact Incident Requirement Test Case Test Set that the log message references See section 5 2 4 for information on how to link a revision with a TFS check in or other action Associations 19 Nov 2014 W Defect found in main form System Administrator This incident was fixed in this revision Incident IN000066 gt Remove gt Add Association 6 2 4 Linking Artifacts
27. ab that shows any artifact associations Throughout SpiraTeam revisions are indicated by the icon Source Code File AutomationEngine cs File Path a2696b980bf38dc63c36cdd5b87692a7247b2f09 File Type Size C Source 18688 KB Last Edited 10 10 2014 3 47 06 PM Author dmarkovtsev Latest Revision Aj 900ab7ec0e Preview Revisions gt Refresh Apply Filter Clear Filter rr eee O 5bfb75478c Adam Sandman Fixes IN 002943 1 Oct 2014 Yes Yes O 900ab7ec0e dmarkovtsev Merge branch master of http git inflectra com 10 Oct 2014 Yes Yes Show 15 rows per page i 1 Displaying page a a of 1 gt pb 8 2 3 Revision Details By clicking on a revision in SpiraTeam you will be taken to the revision details page S y Inflectra Products gt Rapise Planning Testing Tracking Reporting BR system Administrator Source Code gt Revision Details lt lt Back to Revision List md Current Branch gt master v 4 AutomationEngine cs A 900ab7ec0e A 5bfb75478c Source Code Revision 5bfb75478c Notes Fixes IN 002943 Edited By Adam Sandman ContentA Yes Build F Rapise Master 208 Properties A Yes Last Edited 10 1 2014 12 07 38 PM Files Associations gt Refresh Apply Filter Clear Filter Action AY Last Edited AY I aa ee ee eee O Autom ationEngine cs 18688 KB dmarkovtsev 900ab7ec0e Modified 10 Oct 2014 O RunTestThread cs 879
28. ame you can download the specified revision of the file to your local machine This does not do a TFS checkout you are merely downloading the file to your local machine External Projects gt Sample Application Two Planning Testing Tracking Reporting 2 System Administrator Resources Source Code Fila Details lt lt Dack to File List Current Branch jf Main amp Test Project for TFS Source SF App conn a p Source Code File Program cs d Form cs a it Form Designer cs mii Fai aces Pees Tes Ers a 4 Program cs File Type Size Gl Souren iii KB Last Edited VWs 4 17 oe ed A Test Project for TES Source esproj Furlhor INFLEC TRAM sandman Lilies Hivss ri Fh E i Test Projact for TFS Source csproj preview a Amisions Assncinices using System using Syst em Collections Generic using System Ling using System Threading Tasks using System Windonws rm namespace Test Project for TFS Source static class Program try point for the application fff c summary gt STaThread static woid Maint pplication FnableVisualstyles application SetCompatibleTextRenderingDefoult false Spplication un new Form s Underneath the file details is a preview of the contents of the source code file with syntax coloring to make it easier to read In addition there are two other tabs that display the list of all the revisions made to this file and any associations with other SpiraTeam a
29. ation package from the Add Ons Downloads section of the Inflectra website http www inflectra com Spiraleam Downloads aspx and run the installation package on each workstation that has Visual Studio installed Once this installation has been completed you need to tell Visual Studio to add the custom check in policy 1 Inside Visual Studio go to Team gt Team Project Settings gt Source Control to open up the Source Code extensions dialog box Source Control Settings Library Information System 2 Multiple check out allows more than one person to edit a file at the same time Conflicting changes are reconciled before check in Enable multiple check out Get latest on check out downloads the copy of an item from the Team Foundation Server to the client computer This Team Foundation Server setting applies to all items in this team project C Enable get latest on check out 2 Click on the Check in Policy tab to list the various check in policies Source Control Settings Library Information System 2 Check out Settings Check in Policy Check in Notes Policy Type Description 3 Click on the Add button to add a new check in policy Add Check in Policy Check in policy Description Checks TFS check in notes to make sure they contain a reference to a Spira ID task incident or requirement 4 Select the SpiraTeam Plan TFS check in Policy and click OK This will bri
30. cs LogCommand cs LoginCommand cs RemoveCommand cs l drakmar Added an author attribute updated author on each 14 Jan 2005 Yes drakmar Added log console command Log is doing a recursi 3 Dec 2004 Yes drakmar Moved XmiLogCommand to XmiLogCommandParser still 26 Jul 2004 Yes drakmar Fixed bug in date parser routine was not bringing 25 Jul 2004 Yes drakmar Changed the LogReportCommand to use the rlog if a 25 Jul 2004 Yes gne Support for filesets added 77 Dec 2003 Yes gne Support for date specification added 11 Nov 2003 Yes drakmar Code reformat 5 Nov 2003 Yes gne ICommandConnection introduced to isolate commands Oct 2003 Yes a my a io KS lo TS es les Ri e a le la R i ke drakmar Moved cvs file modifications to new namespace File 25 May 2003 Yes drakmar 11 May 2003 Yes nooo 0o0 oO oO 00010 FEPCPEEPEECEEE _ Underneath the file details is a list of all the revisions that this file belongs in or was committed to who performed the commit and the log message for the commit Throughout SpiraTeam revisions are indicated by the Icon 4 2 3 Revision Details By clicking on a revision in SpiraTeam you will be taken to the revision details page Welcome System Administrator My Profile Administration Log Out Help _ spiraTeam x My Page Project Home Planning Testing Tracking Reporting incidents Tasks Resources Source Code gt Revision D
31. der tree of the repository is on the left and files in the current selected directory will be listed in the right table Note that this view will always show the current HEAD revision of the repository The file view will display the filename the current revision number of the file and the date of the last commit You can filter and sort on any of the columns as well 4 2 2 Viewing File Details To view the file details click on a file in the right hand side of the repository The file details page displays the details on the selected revision By default it will be the HEAD revision unless you clicked to view the file details from a revision By clicking on the file name you can download the specified revision of the file to your local machine This does not do an CVS checkout you are merely downloading the file to your local machine Welcome System Administrator My Profile Administration Log Qut Help My Page Project Home Planning Testing Tracking Reporting P spiraTeam Incidents Tasks Resources Source Code gt File Details Role Project Owner Source Code File LogCommand cs File Path sharpevslib src IC ShampCode SharpCysl ib Commands LogCommand cs File Type Size C Sharp 15 KB Last Edited 1 14 2005 9 09 21 AM CommitCommand cs vas Not Supported Latest Revision 41 DiffCommand cs Command cs LogCommand cs A ImportModuleCommand cs 2 InitCommand cs A ListCommand
32. e Source Code link under the Tracking tab You will get a screen similar to e inflectra Products Rapise 4 Planning Testing Tracking Reporting Fi System Administrator i I Sonor ode Repository Growser Rules i Relus i Ay Eilne Curtin Branch fe master i aE Rapise Draplayeng 1 13 cut of 13 hiejs in thee current folder bostelberd ES Brandes D E Core A Dumnoni 2 E Environment HG HelpAndSamples ei Installer m amp Biimaps GEIM amp amp Certificates m amp Files i Ga Redist H GS Rapetel auncher oE Supper i E Temp enamed T Sire kT IIL Bl dobuild bat 948 KB tart 4300538499 11 Apr 2014 E dneotun bat 4509 KB drrurkovisey ef 0319606 22 Oct 2014 B a Booleans wos 4715 KE drmatiovisey kitane 19 Jun 2074 Sa 123 Cora anes 17749 KB t nu Br aseti SOs TEA 201 4S H R Egensions acc 36613 KB dirr ko ban kaga 19 Jun 2044 E Bz Help wae 75045 KB tanur EIT 1b 13 Sep 2014 E FP DE wei G2d2 KE dmarkovtsew JG0G05 MHI 17 Jul 2014 i RP Infragistics wis 14685 KA cirie o JEEE HHD TFadul 201d B pa Samples wes 1 2686 KB Liin Pies he Lees Pa sip dlls E BR SPM ws 5140 KB drearkovtsey eS4l0aso 19 Jun 2074 B BR VSChock wes a627 KE Adam sandman a1 toate 21 Apr 2014 iS Ap a was 6447 KA cirie oe S60605 HHD TFadul 2014 5 RI weg 15667 KB cira boi ENA ie E alProvedin Other Operations gt View Ftewigion Loc oOo Oooo oOo oO OOS Slew 15 F iow5 pir pagi 4 4 Displaying
33. e same configuration settings CvsProvider Project Settings Sample Application Two Change Project lt lt Back to Version Control Home Please edit the following project specific settings for the CvsProvider version control provider If you leave any fields blank then the value will be taken from the provider s default settings To stop using this provider on the project just set the Active flag to No below Project Name Sample Application Two Active for Project ves v Connection Info Login Password Domain Custom 01 Custom 02 o Be sure to change the Active field to Yes or the repository will not be available for the current project o Any other settings entered on this page will override and have the same use as the general settings that you created above You would use these settings if you will have more than one project access different code repositories e Initial setup is complete click on the Source Code menu under the Tracking tab to navigate and browse the source code repository 4 2 Using CVS with SpiraTeam While being able to browse the source code repository can be useful in itself the real strength comes from linking artifacts in SpiraTeam including Incidents Requirements and Tasks to revisions checked into the software repository 4 2 1 Viewing the Repository Tree View the source code tree by selecting the Source Code link under the Tracking tab You will ge
34. eads Due to requirement 12 RQ 12 the code for toString in class XMLparser was modified This also fixed Incident 1034 IN 1034 SpiraTeam will automatically detect tokens and will include links to them under the Associations tab for a revision detail 5 3 Troubleshooting While integration with VSS is rather complex behind the scenes as a user you will only receive a couple of errors that will prevent the integration from working e SpiraTeam will not display the login page and there is an error either on the page or in the Application Event Log that says Could not load file or assembly If this error occurs it is most likely that the VssProvider dll or some of its dependent assemblies were not correctly placed in the VersionControl folder of the SpiraTeam installation Spiraleam reports that the login information is incorrect In this case double check the Version Control settings both for the Project which overrides the general settings and the general settings Project settings will over ride the general settings Be sure to use a user that has access to all nodes in the tree starting from the root repository location If you are taken back to the repository screen and given a message saying that the requested file was deleted from the system this means that an attempt was made to view details on a file that was deleted or destroyed in VSS This is a normal condition in the code repository not necessarily a
35. er s workstation The SpiraTeam plug in for Mercurial allows users of SpiraPlan or SpiraTeam hereafter referred to as Spiraleam to be able to browse a Mercurial repository and view revisions linked to SpiraTeam artifacts The plug in will download a read only working copy of the Mercurial repository onto the SpiraTeam server and use that for displaying the list of files folders The list of revisions will be queried dynamically from this local repository on an as needed basis The plug in also performs pull requests from the specified remote repository to ensure that the local repository remains up to date The rest of this section outlines how to install and use the plug in with SpiraTeam Note The plug in will allow users to download and view different revisions of files and view revision logs but no changes to the repository are allowed through the plug in 7 1 Installing the Mercurial Plug In To install the Mercurial Version Control plug in follow these steps e Copy the following files from the plug in zip archive into the VersionControl sub folder of the SpiraTeam installation o MercurialProvider dll o Mercurial Net dll e Log in as the Administrator and go into SpiraTeam main Administration page and click on the Version Control link under System e Click the Add button to enter the Plug in details page The fields required are as follows Edit Provider MercurialProvider lt lt Back to Version C
36. es a mn ee spiraPlan spiraTeam we we SpiraPlan amp SpiraTeam Version Control Integration User Guide Inflectra Corporation Date November 19th 2014 inflectraZ Contents IFT FOGUCUION sonis 1 Integrating with Subversion 2 Integrating with Perforce 7 Integrating with CVS se0e 12 Integrating with VSS 008 18 Integrating with TFS 0 23 Integrating with Mercurial 31 Integrating with Git 00 37 1 Introduction SpiraPlan is a complete Agile Project Management System in one package that manages your project s requirements releases iterations tasks and bugs issues Designed specifically to support agile methodologies such as Extreme Programming XP Scrum DSDM and Agile Unified Process AUP it allows teams to manage all their information in one environment SpiraTeam is an integrated Application Lifecycle Management ALM system that manages your project s requirements releases test cases issues and tasks in one unified environment SpiraTeam contains all of the features provided by SpiraTest our highly acclaimed quality assurance system and SpiraPlan This guide outlines how to use either SpiraPlan or SpiraTeam in conjunction with a variety of Version Control Software Configuration Management tools This guide assumes that the reader is familiar with both SpiraPlan Spira
37. etails Role Project Owner lt lt vi Source Code Revision 1 10 lt LogCommand cs 4 111 Added log console command Log is doing a recursive search no matter what specify not sure what is going on here Updated By drakmar Content Changed Update Date 12 3 2004 8 47 27 AM Properties Changed Associations 14 Jan 2005 Show fis rows per page 4 lt Displaying page h hof 1 gt gt The revision details screen shows the log for the Commit the commit date and author At the bottom of the page are two tabs Files and Associations The Files tab lists all files that were a part of this commit with their full path size latest revision and date of edit The Associations tab shows any artifact Incident Requirement Test Case Test Set that the log message references See section 3 2 4 for information on how to link a revision with a CVS Commit 29 Dec 2009 W Cannot log into the application Fred Bloggs Incident INQO0058 29 Dec 2009 j Sample Requirement Fred Bloggs Requirement RQ000028 29 Dec 2009 Sample Test Joe P Smith Test Case TCOO0014 4 2 4 Linking Artifacts Linking an artifact is quite simple To maintain the readability of CVS commit messages we adopted a square bracket token The token is in the format of lt artifact identifier gt lt artifact id gt The first half the Artifact Identifier is a two letter code that is used throughout SpiraTeam and is visible on almost every page in the appl
38. f branches files folders revisions The plug in also performs pull requests from the specified remote repository to ensure that the local bare repository remains up to date The rest of this section outlines how to install and use the plug in with SpiraTeam The current version of the Git plugin requires SpiraPlan or SpiraTeam v4 2 0 2 or later Note The plug in will allow users to download and view different revisions of files and view revision logs but no changes to the repository are allowed through the plug in 8 1 Installing the Git Plug In To install the Git Version Control plug in follow these steps e Copy the following files from the plug in zip archive into the VersionConitrol sub folder of the SpiraTeam installation o GitProvider dll o _Inflectra Global dll o LibGit2Sharp dll e f your server operating system is 64 bit then copy git2 d11 from the x64 directory of the downloaded plug in zip file into the VersionControl sub folder of the SpiraTeam installation Note Do not create an x64 folder under VersionControl make sure the file lives in the VersionControl folder itself e f your server operating system is 32 bit then copy git2 d11 from the x32 directory of the downloaded plug in zip file into the VersionControl sub folder of the SpiraTeam installation Note Do not create an x32 folder under VersionControl make sure the file lives in the VersionControl folder itself
39. gistered trademarks of Microsoft Corporation Subversion is a registered trademark of Collabnet Inc All other trademarks and product names are property of their respective holders Please send comments and questions to Technical Publications Inflectra Corporation 8121 Georgia Ave Suite 504 Silver Spring MD 20910 4957 U S A support inflectra com
40. i a nnn Name Su bversionProvider Description Integrates with our internal Subversion instance Active Default Settings The following settings are used for any projects that do not define their own settings Connection Info syn ocal inflectra com bii Password Oe o Name The name must be SubversionProvider o Description The description is for your use only and does not affect operation of the plug in o Active If checked the plug in is active and able to be used for any project o Connection Info This field holds the root of the repository for any project accessing the plug in unless overridden in the Project Settings Start the connection string with svn http orhttps o Login Password The user id and the password of the user to use while accessing and retrieving information from the Subversion server o Custom1 This field is used for deugging Please leave it blank unless specified by support o Other Fields The other fields Domain Custom2 Custom5 are not used by the plug in and will be ignored e When finished click the Insert button and you will be taken back to the Version Control integration list page with SubversionProvider listed as an available plug in e Verify that you are in the correct project using the drop down at top and click on the Project Settings link for the SubversionProvider You will get a screen listing all the same configuration settings
41. ication For example a requirement s identifier is RQ Incidents are IN and test cases are Tc The artifact ID is the number of the artifact So by creating a commit message that reads Due to requirement 12 RQ 12 the code for toString in class XMLparser was modified This also fixed Incident 1034 IN 1034 Spiraleam will automatically detect tokens and will include links to them under the Associations tab for a revision detail 4 3 Troubleshooting While integration with CVS is rather complex as a user you will only receive a couple of errors that will prevent the integration from working e When you first load the list of folders and files for a repository it may take several minutes to load as it s downloading the entire repository from the CVS server to the SpiralTeam server This delay will not occur on subsequent views of the page e Spiraleam will not display the login page and there is an error either on the page or in the Application Event Log that says Could not load file or assembly If this error occurs it is most likely that the CvsProvider dll or some of its dependent assemblies were not correctly placed in the VersionControl folder of the SpiraTeam installation e Spiraleam reports that the login information is incorrect In this case double check the Version Control settings both for the Project which overrides the general settings and the general settings Project settings will
42. ist of the depot The file view will display the filename the current change number of the file the author of the last change and the date of the last change You can filter and sort on any of the columns as well 3 2 2 Viewing File Details To view the file details click on a file in the right hand side of the screen The file details page displays the details on the selected file By default it will be the HEAD change unless you clicked to view the file details from a change By clicking on the file name you can download the specified change version of the file to your local machine This does not open the file on the depot you are merely downloading the file to your local machine Source Code File toned_bar_search gif File Fath lpublic images OT decoltoned _bar_search gif File Type Size GIF Image Fay 0 KB Last Edited S F 2007 12 15 12 AM Author rlo Latest Revision 4 6027 Y Revision AV Author AY Summary AV Commi Date AV Content a AY Propertion 8 AY a v An E ry 6027 rlo submitted CSS amp image files make 17 Sep 2007 Yes No it into public show rows per page Hi lt i Displaying page Sofie h Underneath the file s details is a list of all the changes that this file was changed in who performed the change and the log message for the change Throughout SpiraTeam changes are indicated by the i icon 3 2 3 Change Details By clicking on a change in SpiraTeam you will be taken to the change
43. list details page Source Code Revision 602 submitted CSS amp image files make it into public depot again yikes Updated By rlo Content Changed Update Date 9 17 2007 12 15 12 AM Properties Changed segt iations E i E 7 public css depot css Added 17 Sep 2007 E y public css pure css Added 17 Sep 2007 The revision details screen shows the log for the change the change date and author At the bottom of the page are two tabs Files and Associations The Files tab lists all files that were a part of this change with their full path and the action that was performed on them for this change Possible values are Added Modified Deleted or Other The Associations tab shows any artifact Incident Requirement Test Case Test Set that the log message references See section 2 2 4 for information on how to link a revision with a Perforce change Files 29 Dec 2009 W Cannot log into the application Fred Bloggs Incident INO00056 29 Dec 2009 Sample Requirement Fred Bloggs Requirement RQ000026 29 Dec 2009 Sample Test Joe P Smith Test Case TCO00014 3 2 4 Linking Artifacts Linking an artifact is quite simple To maintain the readability of Subversion s change messages we adopted a bracket token The token is in the format of lt artifact i dentifier gt lt artifact id gt The first half the Artifact Identifier is a two letter code that is used throughout SpiraTeam and is visible on a
44. lmost every page in the application For example a requirement s identifier is RQ Incidents are IN and test cases are Tc The artifact ID is the number of the artifact So by creating a change message that reads Due to requirement 12 RQ 12 the code for toString in class XMLparser was modified This also fixed Incident 1034 IN 1034 SpiraTeam will automatically detect tokens and will include links to them under the Associations tab for a revision detail 3 3 Troubleshooting While integration with Perforce is rather complex as a user you will only receive a couple of errors that will prevent the integration from working SpiraTeam will not display the login page and there is an error either on the page or in the Application Event Log that says Could not load file or assembly This simply means that not all of the required DLL libraries listed above in 3 1 are present in the VersionControl directory inside of the installation It could also mean that the IIS Application Pool is not set to allow 32 bit applications At this time there are no 64 bit DLLs available for the Perforce Provider Spiraleam reports that the login information is incorrect In this case double check the Version Control settings both for the Project which overrides the general settings and the general settings Project settings will over ride the general settings Be sure to use a user that has access to all nodes in
45. m 01 This should contain the name of the equivalent team project in TFS o Custom 02 05 are not used by the TFS plug in and can be ignored o Any other settings entered on this page will override and have the same use as the general settings that you created above You would use these settings if you will have more than one project access different code repositories e Initial setup is complete click on the Source Code menu under the Tracking tab to navigate and browse the source code repository 6 2 Using TFS with SpiraTeam Whilst being able to browse the source code repository can be useful in itself the real strength comes from linking artifacts in SpiraTeam including Incidents Requirements and Tasks to revisions checked into the TFS repository 6 2 1 Viewing the Repository Tree View the source code tree by selecting the Source Code link under the Tracking tab You will get a screen similar to S External Projects gt Sample Application Two ESSA Planning Testing Tracking Raporting e System Administrator ir Sounor cade Reposkory Groweer ulna Reloesh Yy Eiler Curren Branch fe Main E tata Le ee eve tie OL Ee BuetiProcess Temotates Diglayng 1 6 oul of amp bejs ir the current folder Tesi Project for TFS 5 a Test Project for TESS She AF Test Project for TFS Hm IL H SE Properties fey App config INFLEC TAAL sanders h 12 Nov 2014 Be fest Preyect tor FS
46. m Administrator v Content A Yes Properties A No i 27088 27081 427075 5 Nov 2014 al When creating a new incident the component field __ gt Add Association Elise Brooks Fixed IN 002987 Incident INO02987 2 2 4 Linking Artifacts Linking an artifact is quite simple To maintain the readability of Subversion s commit messages we adopted a bracket token The token is in the format of lt artifact identifier gt lt artifact id gt The first half the Artifact Identifier is a two letter code that is used throughout SpiraTeam and is visible on almost every page in the application For example a requirement s identifier is RQ Incidents are IN and test cases are Tc The artifact ID is the number of the artifact So by creating a commit message that reads Due to requirement 12 RQ 12 the code for toString in class XMLparser was modified This also fixed Incident 1034 IN 1034 SpiraTeam will automatically detect tokens and will include links to them under the Associations tab for a revision detail If you forget to add the association during the commit you can use the Add Association option within Spiraleam to add the association after the fact 2 3 Troubleshooting While integration with Subversion is rather complex as a user you will only receive a couple of errors that will prevent the integration from working e Spiraleam will not display the login page
47. n error with VSS or SpiraTeam If you have the VSS database located on a remote file share on a separate server to SpiraTeam you will need to modify the identify used by the IIS Application Pool running SpiraTeam By default the IIS Application Pool will run as the special Windows user NETWORK SERVICE Whilst this is a secure account with low privileges for normal use of the system it may not have sufficient permissions to access the VSS repository over your Local Area Network LAN We recommend changing the IIS Application Pool to instead run as a Windows Domain user that has permissions to access the remote file share containing the VSS database 6 Integrating with TFS Microsoft Visual Studio Team System VSTS Team Foundation Server TFS from Microsoft hereafter referred to as TFS is a Software Configuration Management SCM system that enables users to work on code simultaneously while preserving previous versions by avoiding collisions in code edits This plug in will allow users of SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam to be able to browse a TFS repository and view revisions linked to Spiraleam artifacts There are separate plug ins for TFS 2005 2008 2010 and 2012 When connecting to a TFS 2010 2012 repository the connection URL will also need to be in a different format see below While users working on the code will usually have a complete copy of the repository on their local systems this plug i
48. n will access the TFS repository remotely The rest of this section outlines how to install and use the plug in with SpiraTeam Note The plug in will allow users to download and view different revisions of files and view revision logs but no changes to the repository are allowed through the plug in 6 1 Installing the TFS Plug In To install the TFS Version Control plug in follow these steps e Download the appropriate TFS provider from the Inflectra website http www inflectra com Spira leam Downloads aspx there are separate versions for TFS 2005 2008 2010 and TFS 2012 or later e Copy the following files from the plug in zip archive into the VersionControl sub folder of the SpiraTeam installation o Microsoft TeamFoundation Client dll Microsoft TeamFoundation Common dll Microsoft TeamFoundation Common Library dll Microsoft TeamFoundation dll Microsoft TeamFoundation VersionControl Client dll Microsoft TeamFoundation VersionControl Common dll Microsoft TeamFoundation VersionControl Common ntegration dll o _TfsProvider dll e Log in as the Administrator and go into SpiraTeam main Administration page and click on the Version Control link under System O O O O O 0 e Click the Add button to enter the Plug in details page The fields required are as follows Edit Version Control Provider TfsProvider lt lt Back to Version Control Home Please enter edit the following information for the provider
49. ng up the SpiraTeam custom policy configuration dialog box 5 pira Link Policy Settings Policy Enabled Spira Server htto 4inflactrasyvs S piralT eam Spirra Login I fredbloggs Spira Project Library Information System v Connect Note The system will look for at least 1 or more Spira Ds when this policy i enabled But all IDs fitting these patterns will be queried in Spira to confirm they exist Enforce Links to Tasks Format ITE HAHAH Enforce Links to Incidents Format IN HHHHHE 5 Enter the URL for the SpiraTeam server you only need the server name and virtual directory portion as well as a valid login and password Then click Connect to get the list of projects 6 Select the checkboxes for which artifact tyoes you want to be included in the artifact enforcement and click the OK button to confirm the settings 7 Now when auser checks in a change to the TFS source code repository they will be required to enter at least one SpiraTeam artifact and the system will check to make sure that artifact actually exists in the specified project 7 Integrating with Mercurial Mercurial is a Distributed Version Control System DVCS system that keeps track of software revisions and allows many developers to work on a given project without necessarily being connected to a common network since it doesn t rely on a central repository but instead distributes copies of the entire source code repository to each us
50. nitial setup is complete click on the Source Code menu under the Tracking tab to navigate and browse the source code repository 7 2 Using Mercurial with Spirateam While being able to browse the source code repository can be useful in itself the real strength comes from linking artifacts in SpiraTeam including Incidents Requirements and Tasks to revisions checked into the software repository 7 2 1 Viewing the Repository Tree View the source code tree by selecting the Source Code link under the Tracking tab You will get a screen similar to Welcome System Administrator Lirary information System Y My Profile Administration Log Out Search 19 Help ee spiraTeam My Page Project Home Planning Testing Tracking Reporting Source Code Role Project Owner A https bitbucket org aragost javahg amp javaha alj IL a JIL a Cil _A B scripts BS settings 36 main 2B jaa al 4 BaseRepository java i B Bookmark java B Bundle java ER Changeset java Jan Sorensen Jan Sorensen Jan Sorensen Jan Sorensen 815e3b88f667 54 ObceSaalfcc3 2064635c4 3c 13 Feb 2012 5 Feb 2012 13 Feb 2012 13 Feb 2012 19 Jan 2012 aA com 8 DateTime java aragost E MercuralExtension java Jan Sorensen 49ae 1b0e2e62 21 Jul 2011 javahg N 2 overiavRevository ieve Jan Sorensen 5f8aa17d6a34 13 Feb 2012 6 commands Jan Sorensen 9fb4 16943311 4 Feb
51. nload the specified revision of the file to your local machine This does not do a VSS checkout you are merely downloading the file to your local machine ET Pine e Welcome System Administrator My Profile Administration Log Out Help spiraTeam S My Page Project Home Planning Testing Tracking Reporting Incidents Tasks Resources Source Code gt File Details Role Project Owner Source Code File License txt File Path S NAnt Gui License txt File Type Size Text 0 KB Last Edited 2 4 2010 11 17 28 AM Latest Revision amp 3 Ga Checked in by QO fix issue with incid 4 Feb 2010 Ca Checked in S NAnt Gui 4Feb 2010 Admin Added initial code branch 3 Feb 2010 Show fis Y rows per page 4 lt 4 Displaying page of 1 gt bi Underneath the file details is a list of all the revisions made to this file who performed the revision and the log message for the action performed Throughout SpiraTeam revisions are indicated by the wa icon 5 2 3 Revision Details By clicking on a revision in SpiraTeam you will be taken to the revision details page e Welcome System Administrator My Profile Administration Log Out Help spiraTeam My Page Project Home Planning Testing Tracking Reporting Incidents Tasks Resources Source Code gt Revision Details Role Project Owner lt lt visi Source Code Revision 2 License txt 43 Notes Checked in S NAnt Gui 4 2 41 Updated By kee a Content
52. on on how to link a revision with a Mercurial changeset Files into pli Fred Bloggs Incident INQOO05s 29 Dec 2009 Sample Requirement Fred Bloggs Requirement ROQOO002s 29 Dec 2009 AY sample Test Joe P Smith Test Case TC000014 29 Dec 2009 Cannot log ir 7 2 4 Linking Artifacts Linking an artifact is quite simple To maintain the readability of Mercurial changeset messages we adopted a square bracket token The token is in the format of lt artifact identifier gt lt artifact id gt The first half the Artifact Identifier is a two letter code that is used throughout SpiraTeam and is visible on almost every page in the application For example a requirement s identifier is RQ Incidents are IN and test cases are Tc The artifact ID is the number of the artifact So by creating a commit message that reads Due to requirement 12 RQ 12 the code for toString in class XMLparser was modified This also fixed Incident 1034 IN 1034 Spiraleam will automatically detect tokens and will include links to them under the Associations tab for a revision detail 7 3 Troubleshooting While integration with Mercurial is sophisticated behind the scenes as a user you will only receive a couple of errors that will prevent the integration from working e When you first load the list of folders and files for a repository it may take several minutes to load as it s cloning the entire repository from
53. ontrol Home Please enter edit the following information for the provider The exact information that needs to be entered is specific to each provider and you should refer to the documentation for the provider when entering changing it Name MercurialProvider Description Default Settings The following settings are used for any projects that do not define their own settings Connection https bitbucket org aragost javahg Info Password Domain Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 o Name The name must be MercurialProvider o Description The description is for your use only and does not affect operation of the plug in o Active If checked the plug in is active and able to be used for any project o Connection Info This field holds the clone URL of the repository for any project accessing the plug in unless overridden in the Project Settings For example httpes bitbucket org aragost javahg ssh example com hg o Login Password The user id and the password of the user to use while accessing and retrieving information from the remote Mercurial repository If you are accessing a public repository anonymously just use anonymous for both username and password and it will be handled correctly o Custom 01 This needs to contain the path on the SpiraTeam server where the Mercurial executable Hg exe can be found If left blank it will at
54. p Documents Custom 05 Edit Types NE Cdit Calda o Name The name must be GitProvider o Description The description is for your use only and does not affect operation of the plug in o Active If checked the plug in is active and able to be used for any project o Connection Info This field holds the clone URL of the repository for any project accessing the plug in unless overridden in the Project Settings For example git gqithub com henon GitSharp git hLipt oqiChub com iser repo0 git o Login Password The user id and the password of the user to use while accessing and retrieving information from the remote Git repository If you are accessing a public repository anonymously just use anonymous for both username and password and it will be handled correctly o Custom 01 By default SpiraTeam will store a copy of the Git working directory in the C Program Data Inflectra Spira GitProvider URL folder where URL is the Git connection URL If you would like to use an override location for the Git repository you should specify it in this setting e g C Git Repositories o Custom 02 Custom 05 Not used by this plugin e When finished click the Insert button and you will be taken back to the Version Control integration list page with GitProvider listed as an available plug in e Verify that you are in the correct project using the drop down at top and click on the Project
55. r cs Source Code File ArtifactLinkManager cs FileTypeManager cs namespace Inflectra SpiraTest Business lt summary gt This class encapsulates all the data access functionality for creating and retrieving static links associations between different artifacts lt summary gt public class ArtifactLinkManager ManagerBase private const string CLASS NAME Inflectra SpiraTest Business ArtifactLinkManager lt summary gt Retrieves a set of linked artifacts where the provided one is the source lt summary gt lt param name sourceArtifactType gt The type of the artifact we want to look for links from lt param gt lt param name sourceArtifactId gt The ID of the artifact we want to look for links from lt param gt lt param name destArtifactType gt The type of the artifact we want to look for links to lt param gt Underneath the file details are tabs that show a preview of the file with syntax highlighting a list of all the revisions that this file belongs in or was committed to who performed the commit and the log message for the commit and a tab that shows any artifact associations Throughout SpiraTeam revisions are indicated by the 4 icon Source Code File Automation cs File Path File Type Size C Source 34 KB Author asandman Revisions svn ocal inflectra com SpiraTeam Trunk Business Automation cs Last Edited 8 14 2014 1
56. ra Products Spiraleam Space Fi Planning Testing Tracking Hrporting 2 System Administrator Source Code Raposltory Browser efresh B Refresh ff Fllter Current Branch fe Trunk B E Spra lwin EE Branches Displaying 1 15 oui of 51 file s in the current falder Business E Week wo File name A Siza An j Author Latest ii Last Edited Gavi 2 00 i A i 1 vd ni See 0 0 0 4 AnifaciLinkManager cs mmorrey aos B Sep 20td AE v1 00 Ooh BD sitactiiececet ce asandman 7586 12 Jun 2014 ir s FES egn w ee nar ara 0 j a amp Documentation d Attachment cs ees is decal BGS Releases w Aaemation Perr ahaniman HATS 1g d i Ga Research manimnan Ara JUAN a m ES Support dsandan A545 23 Fug AHA ES Tags E Sa Testing B Ea Think MMorey ards 12 May 2011 AGAMA wadi 19 i asaba 29 Sop sl4 SubversionProvider dsandman Tha 20 Och 011 Other Operations View Revision Lag asandman 25403 1 Jun 20 14 asandman 25925 18 Jun 2014 abandman Arisa E Mow 2014 akandimani fh t hinad ODO ooo aera Hayy Pte oo Sahota 15 F w p r page i a Displaying page 1 Seof dm The folder tree of the repository is on the left and files in the current selected directory will be listed in the right table Note that this view will always show the current HEAD revision of the repository The file view will display the filename the current revision number of the file the author of the last commit and the date of the last commit You
57. ration settings VssProvider Project Settings Library Information System Change Project lt lt Back to Version Control Home Please edit the following project specific settings for the VssProvider version control provider If you leave any fields blank then the value will be taken from the provider s default settings To stop using this provider on the project just set the Active flag to No below Project Name Library Information System Active for Project ves Connection Info Login Password o Be sure to change the Active field to Yes or the repository will not be available for the current project o Any other settings entered on this page will override and have the same use as the general settings that you created above You would use these settings if you will have more than one project access different code repositories e Initial setup is complete click on the Source Code menu under the Tracking tab to navigate and browse the source code database 5 2 Using VSS with SpiraTeam While being able to browse the source code repository can be useful in itself the real strength comes from linking artifacts in SpiraTeam including Incidents Requirements and Tasks to revisions checked into the VSS database 5 2 1 Viewing the Repository Tree View the source code tree by selecting the Source Code link under the Tracking tab You will get a screen similar to Welcome System Administrator
58. roject access different code repositories e Initial setup is complete click on the Source Code menu under the Tracking tab to navigate and browse the source code repository 3 2 Using Perforce with SpiralTeam While being able to browse the source code repository can be useful in itself the real strength comes from linking artifacts in SpiraTeam including Incidents Requirements and Tasks to revisions checked into the software repository 3 2 1 Viewing the Repository Tree View the source code tree by selecting the Source Code link under the Tracking tab You will get a screen similar to Welcome System Administrator My Profile Administration Log Out Library Information System 7 Help ar_ spiraTeam My Page Project Home Planning Testing Tracking Reporting Incidents Tasks Resources Source Code Role Project Owner ree Ee Mem tf Sie Hier B lh aess Revision AY theses Ys E jipublic aL o o M E A l css o e p4 py 4 KB laura_wingerd 157 18 Jun 1999 images E B P4Ciientmodulece 13 KB laura_wingerd 157 18 Jun 1999 jam e E amp perforce a amp api Show rows per page 14 lt Displaying page Fa of 1 gt PI java T review py 12 KB laura_wingerd 18 Jun 1999 amp cdsp4 The folder tree of the repository is on the left and files in the current selected directory will be listed in the right table Note that this view will always show the current HEAD changel
59. rs to download and view different revisions of files and view revision logs but no changes to the repository are allowed through the plug in 4 1 Installing the CVS Plug In To install the CVS Version Control plug in follow these steps e Copy the following files from the plug in zip archive into the VersionControl sub folder of the SpiraTeam installation o CvsProvider dll o DocsVision Remoting dll o ICSharpCode SharpCvs_Lib dll o ICSharpCode SharpZipLib dll o log4net dll e Log in as the Administrator and go into SpiraTeam main Administration page and click on the Version Control link under System e Click the Add button to enter the Plug in details page The fields required are as follows CvsProvider Active Default Settings The following settings are used for any projects that do not define their own settings Connection Info sharpcvslib cvs sourceforge net cvsroot sharpevslib Login anonymous Password Domain Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 o Name The name must be CvsProvider o Description The description is for your use only and does not affect operation of the plug in o Active If checked the plug in is active and able to be used for any project o Connection Info This field holds the root of the repository for any project accessing the plug in unless overridden in the Project Settings Please use the following format
60. rtifacts Preview Revisions gt Refresh Apply Filter Clear Filter Z Ben SY ther AS Sey ii i Commit Date AY ContentA AY Coo JO JLU No o As INFLECTRA adam sandman test commit 12 Nov 2014 No Show 15 Y rows per page i Displaying page a of 1 gt PI The revision list will display the name of the revision who performed the revision and the log message for the action performed Throughout SpiraTeam revisions are indicated by the i icon Associations 19 Nov 2014 B Defect found in main form System Administrator This defect relates to this file Incident IN000066 gt Remove gt Add Association The association list will display the list of SpiraTeam artifacts that are linked to this specific source code file You can add a new association by clicking on the Add Association hyperlink 6 2 3 Revision Details By clicking on a revision in SpiraTeam you will be taken to the revision details page S y External Projects v gt Sample Application Two Planning Testing Tracking Reporting E Administrator Source Code gt Revision Details lt lt Back to Revision List nd Current Branch Main v Program cs Source Code Revision 415 Notes test commit Edited By INFLECTRA adam sandman Content A No Build Properties A No Last Edited 11 12 2014 11 29 24 AM Files Associations gt Refresh Apply Filter Clear Filter Ei SizeAY Author A
61. s lt lt Back to File List Y Source Code File Bundle java amp javahg 2 BaseRepository java File Path src main iava convaragost iavahg Bundle java Bookmark java File Type Size Java Source 3338 KB 4 Bundle java Author Sos Soa 2 Changeset java 2 DateTime java Associations 2 MercunialExtension java OverlayRepository java 2 Phase java Repository java 2 RepositoryConfiguration java UnknownCommandException java 2 WorkingCopy java e spiraTeam S Role Project Owner 2 13 2012 7 40 02 AM A 5f8aa 1796234 amp 58221746234 Jan Sorensen OverlayRepositoryTest Some test cases for Overlay 13 Feb 2012 Yes 4 407090ab3b20 Jan Sorensen Merge 19 Jul 2011 Yes amp opap797a740 Martin Geisler Added missing license headers 19 Jul 2011 Yes M AD te7tiass7985 F amp 74eba0880201 40514000390 Jan Sorensen Jan Sorensen Jan Sorensen Added license headers Repository Created two subclasses BaseRepository Server Reference count to stop server for overlay 19 Jul 2011 19 Jul 2011 18 Jul 2011 Yes amp 7855d21c99e1 Jan Sorensen IncomingCommand Return Bundle object 18 Jul 2011 Show 15 Y rows per page 4 lt Displaying page 1 of 1 gt Underneath the file details is a list of all the revisions Mercurial changesets that this file belongs in or was committed to who performed the commit and the log message for the commit Thro
62. s RQ Incidents are IN and test cases are Tc The artifact ID is the number of the artifact So by creating a commit message that reads Due to requirement 12 RQ 12 the code for toString in class XMLparser was modified This also fixed Incident 1034 IN 1034 Spiraleam will automatically detect tokens and will include links to them under the Associations tab for a revision detail If you forget to add the association during the commit you can use the Add Association option within Spiraleam to add the association after the fact 8 3 Troubleshooting While integration with Git is sophisticated behind the scenes as a user you will only receive a couple of errors that will prevent the integration from working e When you first load the list of folders and files for a repository it may take several minutes to load as it s cloning the entire bare repository from the remote Git server to the SpiraTeam server This delay will not occur on subsequent views of the page e SpiraTeam will not display the login page and there is an error either on the page or in the Application Event Log that says Could not load file or assembly If this error occurs it is most likely that the GitProvider dll or some of its dependent assemblies were not correctly placed in the VersionControl folder of the SpiraTeam installation e SpiraTeam reports that the login information is incorrect In this case double check
63. s not exist Unless you have a client pre defined for the plugin we recommend using the default PerforceProvider Custom02 The base depot or root directory must be entered here Other Fields The other custom fields Custom03 Custom05 are not used by the plug in and will be ignored e When finished click the Insert button and you will be taken back to the Version Control integration list page with PerforceProvider listed as an available plug in e Verify that you are in the correct project using the drop down at top and click on the Project Settings link for the PerforceProvider You will get a screen listing all the same configuration settings PerforceProvider Project Settings Library Information System Change Project lt lt Back to Version Control Home Please edit the following project specific settings for the PerforceProvider version control provider If you leave any fields blank then the value will be taken from the provider s default settings To stop using this provider on the project just set the Active flag to No below Project Name Library Information System Active for Project Yes O Be sure to change the Active field to Yes or the repository will not be available for the current project Any other settings entered on this page will override and have the same use as the general settings that you created above You would use these settings if you will have more than one p
64. sandman asandman asandman asandman a ArtifactLinkManager cs mmorrey 2 ArtifactLinkType cs 4 ArtifactLinkView cs asandman asandman NWOVOJOVO O O O O OVO Modified Modified Modified Modified Modified Modified Modified Modified Modified es 11 Sep 2014 11 Sep 2014 11 Sep 2014 11 Sep 2014 11 Sep 2014 11 Sep 2014 8 Sep 2014 11 Sep 2014 11 Sep 2014 The revision details screen shows the log for the Commit the commit date and author At the bottom of the page are two tabs Files and Associations The Files tab lists all files that were a part of this commit with their full path and the action that was performed on them for this commit Possible values are Added Modified or Deleted The Associations tab shows any artifact Incident Task Requirement Test Case Test Set etc that the log message references See section 2 2 4 for information on how to link a revision with a Subversion Commit Planning Testing Tracking Reporting Source Code gt Revision Details S y Inflectra Products gt Spiraleam o lt lt Back to Revision List x 27154 27153 4 27138 4 27133 27131 27130 427125 427107 Current Branch gt Irunk v A Source Code Revision 4 27130 Notes Fixed IN 002987 Edited By 27106 Build SpiraTeam Trunk 434 427095 Last Edited 11 5 2014 7 01 03 PM A 27091 a Files 27090 asandman Associations 2 Syste
65. stall the Subversion Version Control plug in follow these steps e Copy the following files into place on your Web Server s SpiraTeam installation o Copy the file SubversionProvider dll file into the VersionControl sub folder of the SpiraTeam installation o If your server operating system is 64 bit then copy all the files in the x64 directory of the downloaded plug in zip file into the VersionControl sub folder of the SpiraTeam installation Note Do not create an x64 folder under VersionControl make sure the files live in the VersionControl folder itself o If your server operating system is 32 bit then copy all the files in the x32 directory of the downloaded plug in zip file into the VersionControl sub folder of the SpiraTeam installation Note Do not create an x32 folder under VersionControl make sure the files live in the VersionControl folder itself e Log in as the Administrator and go into SpiraTeam main Administration page and click on the Version Control link under System e Click the Add button to enter the Plug in details page The fields required are as follows Edit Version Control Provider SubversionProvider lt lt Back to Version Control Home Please enter edit the following information for the provider The exact information that needs to be entered is specific to each provider and you should refer to the documentation for the provider when entering changing it
66. t a screen similar to P spiraTeam See My Page Project Home Planning Testing Tracking Reporting Incidents Tasks Resources Source Code sharpcvslib cvs sourceforge net cvsroo sharpcvslib _extemalToolBuilders H amp build cont 2 doc ext license NetCapture style testing E www images H style AddCommand cs Not Supported CheckoutModuleCommand cs Not Supported CommitCommand cs Not Supported DiffCommand cs Not Supported iCommand cs Not Supported 4 lLogCommand cs Not Supported 2 importModuleCommand cs Not Supported 2 InitCommand cs Not Supported 2 ListCommand cs Not Supported a LogCommand cs Not Supported 4 LoginCommand_cs Not Supported RemoveCommand cs Not Supported RetreiveFilelistCommand cs Not Supported examples lib B sre 3 CvsLib amp iCSharpCode amp SharpCvsLib iCSharpCode Console iCSharpCode Tests E SharpCvsAddin RTagCommand cs Not Supported RLogCommand cs Not Supported OOO000O 00000 OOOO E Welcome System Administrator My Profile Administration Log Out Role Project Owner 7 Feb 2005 30 Jan 2005 24 Apr 2005 14 Jan 2005 14 Jan 2005 14 Jan 2005 28 Mar 2005 14 Jan 2005 24 Apr 2005 14 Jan 2005 13 Sep 2005 14 Jan 2005 14 Jan 2005 14 Jan 2005 14 Jan 2005 rs SharpCvsAddinSetup Show is Y rows per page 14 lt Displaying page of 2 gt pi w tools The fol
67. t require a username password just use anonymous as both the username and password o Domain This is the Windows Domain that the TFS server is a member of If the machine is not part of a domain you should just use the TFS server name instead If you are connecting to a hosted Visual Studio Online VSO repository you should leave the Domain blank o Custom01 05 are not used by the TFS plug in and can be ignored e When finished click the Insert button and you will be taken back to the Version Control integration list page with TfsProvider listed as an available plug in e Verify that you are in the correct project using the drop down at top and click on the Project Settings link for the TfsProvider You will get a screen listing all the same configuration settings TfsProvider Project Settings Sample Application Two Change Project lt lt Back to Version Control Home Please edit the following project specific settings for the TfsProvider version control provider If you leave any fields blank then the value will be taken from the provider s default settings To stop using this provider on the project just set the Active flag to No below Project Name sample Application Twa Active for Project ves 7 Connection Info Login Password Domain Custom 01 Test Project 1 o Be sure to change the Active field to Yes or the repository will not be available for the current project o Custo
68. tempt to automatically discover Mercurial from the Windows PATH environment variable o Custom 02 Custom 05 Not used by this plugin e When finished click the Insert button and you will be taken back to the Version Control integration list page with MercurialProvider listed as an available plug in e Verify that you are in the correct project using the drop down at top and click on the Project Settings link for the MercurialProvider You will get a screen listing all the same configuration settings MercurialProvider Project Settings Library Information System Change Project lt lt Back to Version Control Home Please edit the following project specific settings for the MercurialProvider version control provider If you leave any fields blank then the value will be taken from the provider s default settings To stop using this provider on the project just set the Active flag to No below Project Name Library Information System Active for Project Connection Info Login Password Domain Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 o Be sure to change the Active field to Yes or the repository will not be available for the current project o Any other settings entered on this page will override and have the same use as the general settings that you created above You would use these settings if you will have more than one project access different code repositories e I
69. the Version Control settings both for the Project which overrides the general settings and the general settings Project settings will over ride the general settings Be sure to use a user that has access to all nodes in the tree starting from the root repository location e f you are taken back to the repository screen and given a message saying that the requested file was deleted from the system this means that an attempt was made to view details ona file that is no longer part of the current branch This can happen when a file is deleted or renamed and this is a normal condition in the code repository not necessarily an error with Git or SpiraTeam 8 4 Data Purging Since the integration with Git requires that a bare copy of the Git repository be stored on the SpiraTeam server you may decide at some point to unlink a disused Git repository from SpiraTeam to save disk space However unlinking the repository through the SpiraTeam web interface will not remove the bare copy of the repository from the server To permanently remove a repository from the SpiraTeam server you need to locate the following path o Windows XP 2003 C Documents and Settings All Users Application Data Inflectra o Windows 2008 7 Vista C ProgramData Inflectra If you look inside this folder you will see a subfolder called Spira and under that will be a subfolder called GitProvider If you open up this subfolder you will see a list of
70. the remote Mercurial server to the SpiraTeam server This delay will not occur on subsequent views of the page e SpiraTeam will not display the login page and there is an error either on the page or in the Application Event Log that says Could not load file or assembly If this error occurs it is most likely that the MercurialProvider dll or some of its dependent assemblies were not correctly placed in the VersionControl folder of the SpiraTeam installation e SpiraTeam reports that the login information is incorrect In this case double check the Version Control settings both for the Project which overrides the general settings and the general settings Project settings will over ride the general settings Be sure to use a user that has access to all nodes in the tree starting from the root repository location e f you are taken back to the repository screen and given a message saying that the requested file was deleted from the system this means that an attempt was made to view details on a file that is no longer part of the TIP branch This can happen when a file is deleted or renamed and this is a normal condition in the code repository not necessarily an error with Mercurial or SpiraTeam 7 4 Data Purging Since the integration with Mercurial requires that a working copy of the Mercurial repository be stored on the SpiraTeam server you may decide at some point to unlink a disused Mercurial repository from Spiraleam to
71. ughout Spiraleam revisions are indicated by the i icon 7 2 3 Revision Details By clicking on a revision in SpiraTeam you will be taken to the revision details page Welcome System Administrator My Profile Administration Log Out Search Help My Page Project Home Planning Testing Tracking Reporting esources Source Code gt Revision Details lt lt Back to Revision List Source Code Revision 4 Sbab787a74ff 1 Bundle java A 5f8aa17d6a34 Added missing license headers d07090ab3b20 A 9bab737a74ff A fa7 idd4785 A 74eba088d2a1 A d05140e039dc amp 7855d21c99e1 e spiraTeam Role Project Owner Martin Geisler Content A Properties A 7 19 2011 9 38 20 AM Martin Geisler apih IncomingCommandTest java Martin Geisler OutaoingCommandTest java Martin Geisler F RepositoryConfiguration java Mantin Geisler Show 15 v rows per page 13 Feb 2012 13 Feb 2012 Sbab787a74ff r 19 Jul 2011 49d6dcfidec4 12 Feb 2012 4 lt Displaying page 1 of 1 gt gt The revision details screen shows the log for the changeset the commit date and author At the bottom of the page are two tabs Files and Associations The Files tab lists all files that were a part of this commit with their full path size latest revision and date of edit The Associations tab shows any artifact Incident Requirement Test Case Test Set that the log message references See section 7 2 4 for informati

SpiraPlan/Team Version Control Integration Guide

Contents

Download Pdf Manuals

Related Search

Related Contents