complete user manual for TaraVault
Contents
1. Passwords amp Security Email Preferences LDAP Settings TaraVault Connection Regional Settings User Login administrator taravault net Project Connection https svnb taravault net inflectratest3 libraryinformationsystem svn User Password Click to show password This page displays the current user s TaraVault login as well as the connection string they should use to connect to the current project the format will depend on whether the user is using Git or Subversion They can click on the Click to show password option to reveal their password This is necessary since they will need to Know the password to use when connecting to Subversion Git using their desired SCM client e g TortoiseSVN TortoiseGit etc 4 Using Subversion Subversion is a version control system VCS also known as a revision control system RCS That is Subversion manages files and directories and the changes made to them over time This allows you to recover older versions of your data or examine the history of how your data changed Some version control systems are also software configuration management SCM systems These systems are specifically tailored to manage trees of source code and have many features that are specific to software development such as natively understanding programming languages or supplying tools for building software Subversion however is not one of these systems It is a general system that can2. master when it is internally stable and all the unit tests pass We shall create a new named branch in our local repository using TortoiseGit To do that right click on the top level folder sampleapplicationone and then click Tortoise Git gt Create Branch EM Switch Checkout Y Merge te Create Branch This will display the following dialog box YY CATemp Git sampleapplicationone Create Branch TortoiseGit Name Branch experimental Base On HEAD master Branch master Tag Commit Options E Track E Switch to new branch Message Doo Enter in the name of the new branch we have chosen experimental in the example shown and click OK to create the new branch Since we want to start working in this new branch we should now using TortoiseGit gt Switch Checkout to switch to this new branch Switch To Branch A Tag E Commit Option Create New Branch Branch experimental E Force El Merge Track Override branch if exists Click OK to confirm the switch Now all your changes will be made on this branch Now let s simulate making a code change on the experimental branch we made To do that change one of the files in the folder structure and then right click Git Commit gt experimental Git Sync A Git Commit gt experimental RE TortoiseGit That will display the comm
3. Action Path Command Update Updating C Temp Subversion ibraryinformationsystem Branches Added C Temp Subversion Vibraryinformationsystem Branches 2 0 0 0 Added C Temp Subversion ibraryinformationsystem Branchesw2 0 0 0 SeleniumSampleTest Added C Temp Subversion Vibraryinformationsystem Branches w2 0 0 0 SeleniumSampleTest Assemblyinfo cs Added C Temp Subversion ibraryinformationsystem Branches w2 0 0 0 SeleniumSampleTest SeleniumSampleTest cs Added C Temp Subversion Vibraryinformationsystem Branches v2 0 0 0 SeleniumSampleTest GoogleTest cs Added C Temp Subversion Vibraryinformationsystem Branches v2 0 0 0 SeleniumSampleTest SeleniumSampleTest ce a LU Added 14 Similarly to make a Tag right click on Trunk and choose TortoiseSVN gt Branch Tag and change the To path from trunk to Tags v1 0 0 0 amp C Temp Subversion libraryinformationsystem Trunk Copy Branch Tag TortoiseS Repository From WC URL https svn6 taravault net inflectratest3 librar yinformationsystem svn Trunk To path fTags v 1 0 0 0 x Destination URL https svn6 taravault net inflectratest3 lbrar yinformationsystem svn Tags v 1 0 0 0 Log message Creating tagged y1 0 Create copy in the repository from HEAD revision in the repository Specific revision in repository Working copy Set explicit revision for these externals Check All None Path URL Revision Fixed atrev
4. You can now copy some code and folders into the Trunk top level folder for your project In this example we shall add some sample Inflectra code SampleTestSuite di SeleniumSampleT est SpiraTestNUnitAddin sin Select all the files and folders and choose TortoiseSVN gt Add then after adding the files and folders choose TortoiseSVN gt Commit to add these files to the repository 4 C Temp Subversion libraryinformationsystem Commit TortoiseSVN Commit to https svn6 taravault net inflectratest3 libraryinformationsystem svn Message A new version of TortoiseSVN is available Please go to http ertoesimnet to get adding codd Changes made double click on file for diff Check All None Non versioned Versioned Added Deleted Modified Files Directories Path Property status Lock di Trunk SampleTestSuite E A Trunk SampleTestSuite AssemblyInfo cs ss c Trunk SampleTestSuite SampleTestFixture cs cs E Trunk SampleTestSuite SampleTestSuite csproj csproj Trunk SampleTestSuite SampleTestSuite csproj user user Hr Show unversioned files Show externals from different repositories Keep locks Keep changelists Now open up one of the files we shall modify the SampleTestSuite AssemblyInfo cs file in our example and make a change to it Then right click on Trunk and choose TortoiseSVN gt Commit to commit the change Make sure you add a comment amp C Temp Subversion libraryinformat
5. No extemals found E Create intermediate folders E Switch working copy to new branch tag La Once that has been completed right click on the Tags folder and choose TortoiseSVN gt Update amp Update Finished a x Action Path Command Update Updating C Temp Subversion ibraryinformationsystem Tags Added C Temp Subversion ibrar yinformationsystem Tags v 1 0 0 0 Added C Temp Subversion ibraryinformationsystem Tags v 1 0 0 0 SeleniumSampleTest Added C Temp Subversion ibrar yinformationsystem Tags v 1 0 0 0 SeleniumSampleTest AssemblyInfo cs Added C Temp Subversion ibrar yinformationsystem Tags v 1 0 0 0 SeleniumSampleTest SeleniumSampleTest csproj Added C Temp Subversion ibrar yinformationsystem Tags v 1 0 0 0 SeleniumSampleTest GoogleTest cs C Temp Subversion ibrar yinformationsystem Tags v 1 0 0 0 SeleniumSampleTest SeleniumSampleTest csproj The main difference between a Branch and a Tag is that you can continue to make changes on a Branch whereas a Tag is a fixed snapshot of the Trunk and cannot be modified To illustrate this let s simulate making a bug fix on the v2 0 branch we made To do that change one of the files in the Branches v1 0 0 0 folder structure and then right click TortoiseSVN gt Commit 4 C Temp Subversion libraryinformationsystem Branches Commit TortoiseSVN Commit to https svn6 taravault net inflectratest3 libraryinformationsystem svn Branches
6. 10 7 2015 4 26 25 PM At this stage we are not ready to Push the repository to TaraVault so just click Close Now open up one of the files we shall modify the SampleTestSuiteiAssemblyInfo cs file in our example and make a change to it Then right click on the top level sampleapplicationone folder and choose Git Commit gt master to commit the change Make sure you add a comment 4 C Temp Git sampleapplicationone SampleTestSuite Commit TortoiseGit Commit to master new branch Message Updated the version number T Amend Last Commit Set commit date Set author Si oft Dy E tho Add Signed off b Changes made double click on file for diff Check All None Unversioned Versioned Added Deleted Modified Files Submodules Path c SampleTestSuite AssemblyInfo cs SS E Show Unversioned Files 1 files selected 1 files total Do not autoselect submodules View Patch gt gt Whole Project Message only Click OK and the change known as a revision will now be committed into the master branch of the local repository 5 5 Working with Branches Now that we have the primary development line in our master branch we can work on a separate version of the code in a different branch and then at a later date merge back in the changes to the master branch For example we might be working on an experimental new feature and we only want to merge it into the
7. Checkout Depth Revision HEAD revision Revision Show log You need to enter the following e URL of repository needs to be the TaraVault connection string listed under My Profile for the current project e Checkout Directory needs to be the local name of the folder for this project Typically it is best to make it the same as the name of the project in TaraVault e g C Temp Subversion libraryinformationsystem In this example When you click on the OK button the following authentication dialog box will appear amp Authentication https svn6 taravault net 43 gt Subversion Repository Requests a username and a password Username administrator taravault net Password CLITZIIIII Save authentication Enter your TaraVault username password choose Save authentication and then click OK You will now get a folder c Temp Subversion libraryinformationsystem that is completely empty apart from a special _svn or svn folder that is used by TortoiseSVN internally Now that you have your Subversion working folder downloaded you should add the following three folders right now e Trunk e Branches e Tags Once you have added them to Windows Explorer select them all and choose TortoiseSVN gt Ada 1 2015 11 40 AM Fil Open Open in new window 10 7 2015 11 40 AM 10 7 2015 11 39 AM Share with Tortoisebit TortoiseSVN Add Add to archive i Add to ignore li
8. Message A new version of TortoiseSVN is available Please go to ses net get updated comment Changes made double dick on file for diff Check All None Non versioned Versioned Added Deleted Modified Files Directories Path Extension Status Property status Lock c v2 0 0 0 SampleTestSuite SampleTestFixture cs cS modified J p Show unversioned files 1 files selected 1 files total Show externals from different repositories Keep locks Keep changelists Click OK and we are now ready to view the repository within Spira 4 5 Viewing within Spira In addition to being able to browse the source code repository in Spira which is itself very useful the real strength comes from linking artifacts in Spira including Incidents Requirements and Tasks to revisions checked into the software repository indicating what was fixed or implemented in a specific revision Firstly you can view the source code tree by selecting the Tracking gt Source Code link under the main Spira menu This will display the following Refresh Y Filter v Current Branch master v Displaying 1 0 out of 0 file s in the current folder No Folder Selected oQ oC es Show rows per page 4 Displaying page Fa of 0 gt gt This is normal it means simply that the source code viewer is initializing for initial use Whenever you access a TaraVault project for the first time you will see this After a few
9. be used to manage any collection of files though it is often used for SCM handling source code files 4 1 Repository Layout Before we get started with using Subversion we need to discuss the standard folder layout For TaraVault to display its branches folders files and revisions correctly in Spira you need to follow this layout for all your Subversion projects These three concepts are explained below e Trunk is the main folder containing all the data This is the main line of current development for the project e A Branch contains copy of the trunk files and directories These are used to denote older or non primary versions of the Trunk You may still commit changes into these branches For example you may be still fixing bugs on an older version whilst primary development is occurring on the latest version e Tags can also be referred as milestone This is a check point to indicate that your project has reached a certain point You can use this to mark various releases Unlike a branch you cannot commit changes into a tag An example setup for such a project could look like Branches v1 0 0 0 v2 0 0 0 v2 1 0 0 v2 2 0 0 The same folders and files are typically stored inside each of the Branches Tags and the Trunk We shall illustrate this more closely when we get started in the next section 4 2 Getting Started with Subversion This section assumes that you have already provisioned at least one Subver
10. the commit you can use the Add Association option within SpiraTeam to add the association after the fact 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 Spira TaraVault SpiraPlan SpiraTeam and Inflectra are either trademarks or registered trademarks of Inflectra Corporation in the United States of America and other countries Microsoft Windows Visual Studio Explorer and Visual SourceSafe are registe
11. 75 gt Add Association Notes Fixed IN 002987 Associations 4 6 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 SpiraTeam to add the association after the fact This is described in more detail in the SpiraTeam User Manual 5 Using 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
12. LaraVault TaraVault Source Code Hosting for Spira User Manual Inflectra Corporation Date October 5th 2015 inflectraZ Contents 1 Introduction TaraVault M is the secure source code and file 1 Introduction escenisdsadiisssssinisiigasissta o 1 hosting service from Inflectra that allows you to host your source code and other assets in our 2 Activating TaraVault 2 secure cloud integrated with our Spira application lifecycle management system 3 Provisioning Projects amp Users 3 g l This guide outlines how to activate and use 4 Using Subversion 8 TaraVault with a cloud based instance of SpiraPlan or SpiraTeam The guide covers the S Using Cl ee ee 19 general activation process in additional to specific sections dedicated to the two supported Legal Notices sececcccecteenscictceeesheneensbeces 30 SCM technologies Git or Subversion This guide assumes that the reader is familiar with both SpiraPlan SpiraTeam and the appropriate SCM platform Git and or Subversion For information regarding how to use SpiraPlan Team please refer to the SpiraPlan User Manual or the SpiraTeam User Manual 2 Activating TaraVault To get started log into your existing SpiraPlan or SpiraTeam instance hereafter referred to as Spira with a system administrator account and go to the main Administration menu SE External Projects gt Sample App
13. Spira user for TaraVault Project Membership Passwords amp Security TaraVault Membership Enable user for TaraVault Now check this box and the following screen appears Project Membership Passwords amp Security TaraVault Membership Enable user for TaraVault TaraVault User Login fredbloggs taravault net TaraVault User Password o Enter in the desired password for TaraVault and click the main Update button and this user will now be added to TaraVault Note that you need to have sufficient TaraVault licenses for all of the users you wish to activate Finally you can now add this user to specific TaraVault projects by clicking on the user s administration page again Project Membership Passwords amp Security TaraVault Membership Enable user for TaraVault TaraVault User Login fredbloggs taravault net 234 59 TaraVault User Password Projects Enabled for this User This user is active but not assigned to any projects Add Projects Add Projects Now click on the Add Projects link and you can now choose which TaraVault projects to add the user to Add User Project Membership Fred Bloggs fredbloggs lt lt Back To User Details The user is not a member of the following TaraVault projects Select the checkbox to add the user to those projects and then click the Add button PR 1 Library Information System You should now click the Add User to Project checkbo
14. ad Putty Key Set upstream track remote branch _ Always push to the selected remote archive for this local branch _ Always push to the selected remote branch for this local branch ters cb Cx In this case we want to push all branches master and experimental to TaraVault so select the checkbox Push all branches Then click OK to push the changes ge CATemp Git sampleapplicationone Git Command Progress Tortoi _o O Es Writing objects hrtps git taravault net intlectratest3 sampleapplicationone g 7 it new branch experimental gt experimental new branch master gt master Success 18237 ma E 10 7 2015 5 48 52 PM Once they have been pushed we are now ready to view the repository within Spira 5 6 Viewing within Spira In addition to being able to browse the source code repository in Spira which is itself very useful the real strength comes from linking artifacts in Spira including Incidents Requirements and Tasks to revisions checked into the software repository indicating what was fixed or implemented in a specific revision Firstly you can view the source code tree by selecting the Tracking gt Source Code link under the main Spira menu This will display the following Refresh Y Filter v Current Branch master v Displaying 1 O out of O file s in the current folder No Folder Selected Show rows per page lt Displaying page Fa of 0 gt gt Th
15. ate 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 29 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 E RapiseLauncher doesn t execute on our internal ser Adam Sandman Fixes IN 002943 Incident IN002943 gt Add Association 5 7 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 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
16. avault net 4 GoogleTest cs 1541 KB administrator taravault net 4 SampleTestFixture cs 1732 KB administrator taravault net E SampleTestSuite cspro 6011 KB administrator Dtaravault net INS IRD IR lw IN 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 the next section for information on how to link a revision with a Subversion Commit S y Inflectra Products gt SpiraTeam Planning Testing Tracking Reporting system Administrator Source Code gt Revision Details lt lt Back to Revision List A Current Branch gt Trunk v 827154 a 827153 Source Code Revision 2127130 27138 827133 827131 8327130 827125 8927107 Edited By asandman ContentA Yes 4 27106 Build al SpiraTeam Trunk 434 Properties A No 4 27095 Last Edited 11 5 2014 7 01 03 PM 827091 e 27090 27088 Date Artifact Name Creator Comment Artifact Type ID Operations 827081 5 Nov 2014 E When creating a new incident the component field Elise Brooks Fixed IN 002987 Incident IN002987 Aj 270
17. e GIT v Client Connection This provides you information on the name and ID of your TaraVault account as well as an indication as to how many source code users your subscription allows If you need to purchase additional users just contact Inflectra customer services who will be happy to help you out Now that your instance is active you will need to provision individual projects and also activate the Spira users that will be allowed to commit code or files into the TaraVault repositories Note All users in Spira will be able to view the files in TaraVault without needing a separate TaraVault license 3 Provisioning Projects amp Users Once you have activated TaraVault for your instance of Spira you can now begin to provision specific projecis and assign users 3 1 Provisioning Projects To provision a new project with TaraVault go to the main Spira Administration page and select the appropriate project and then go to the TaraVault administration page For example in the screenshot below we have selected the Library Information System sample project TaraVault Configuration Library Information System Change Project TaraVault is the hosted source code repository and software configuration management SCM system provided by Inflectra Projects in Spiraleam can be enabled in TaraVault for storage of project source code files and revisions TaraVault is provision You can change which users are active for source cod
18. e Fs of 1 gt gt 4 SampleTestFixture cs 1732 KB administrator taravault net E SampleTestSuite csproj 6011 KB administrator Dtaravault net E SampleTestSuite csproj user 452 KB administrator taravault net IND IN IN IRS Iw To view the file details click on a file hyperlink in the grid The file details page displays the details on the selected file By default it will be the HEAD revision unless you clicked to view the file details from a specific 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 Subversion checkout you are merely downloading the file to your local machine lt lt Back to File List Current Branch f Trunk v amp SampleTestSuite Assemblyinfo cs Source Code File SampleTestFixture cs at SampleTestFixture cs SampleTestSuite csproj File Path SampleTestSuite SampleTestFixture cs E SampleTestSuite csproj user File Type Size C Source c 1732 KB Last Edited 10 7 2015 12 43 21 PM SampleTestSuite nunit Author administrator taravault net Latest Revision 892 Preview Revisions Associations using System using NUnit Framework using Inflectra SpiraTest AddOns SpiraTestNUnitAddIn SpiraTestFramework namespace Inflectra SpiraTest AddOns SpiraTestNUnitAddIn SampleTestSuite lt summary gt Sample test fixture that tests the NUnit SpiraTest integration TestFixture SpiraTestCo
19. e management in the View Edit Users screen TaraVault Global Settings Available TaraVault Users 5 Active TaraVault Users 1 View List TaraVault Account Name inflectratest3 117326 TaraVault Project Settings TaraVault Project Active No TaraVault Project Name TaraVault Project Type Gir 7 Client Connection To provision this project with TaraVault you need to choose the following e Project Name this is the name of the project in TaraVault This name is incorporated into the connection URL so it should be alphanumeric only e Project Type this is the type of SCM repository you wish to use Currently the choices are between Subversion and Git We discuss the differences between Subversion also known as SVN and Git in sections 4 and 5 respectively Note once you choose the repository type for a project it cannot be changed without deleting the entire repository so make sure you understand the differences between the two technologies beforehand For example we will choose libraryinformationsystem as the project name and SVN Subversion as the project type Once you are happy with your choice click Activate to enable this project for TaraVault TaraVault Configuration Library Information System Chang TaraVault is the hosted source code repository and software configuration management SCM system provided by Inflectra Projects in Spiraleam can be enabled in TaraVault for storage
20. epository Specific revision in repository Working copy Set explicit revision for these externals Check All None Revision Fixed atrev No extemals found E Create intermediate folders Switch working copy to new branch tag x Change the To path from Trunk to Branches v2 0 0 0 You can either branch the latest revision called the HEAD revision or a specific revision B C Temp Subversion libraryinformationsystem Trunk Copy Branch Tag TortoiseS Repository From WC URL https svn6 taravault net inflectratest3 lbrar yinformationsystem svn Trunk To path Branches v2 0 0 0 v am Destination URL https svn6 taravault net inflectratest3 libraryinformationsystem svn Branches v2 0 0 0 Log message branching td uz 0 Create copy in the repository from HEAD revision in the repository Specific revision in repository Working copy Set explicit revision for these externals Check All None Revision Fixed atrev No extemals found E Create intermediate folders Switch working copy to new branch tag We also recommend adding a Log message to describe the purpose of making the branch Once you are happy with your choice click OK to confirm the branch Once that is done a copy of the Trunk will now be available under the Branches v2 0 0 0 folder To see this right click on Branches and choose TortoiseSVN gt Update Update Finished
21. 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 lt lt Back to File List Current Branch master v amp SampleTestSuite E Assemblyinfo cs Source Code File Assemblylnfo cs a SampleTestFixture cs o i s IS leTestSuite A blylnfo cs SampleTestSuite csproj File Path ampleTestSuite Assemblylnfo cs SampleTestSuite csproj user File Type Size C Source 2426 KB Last Edited 10 7 2015 4 29 25 PM SampleTestSuite nunit Author Adam Sandman Latest Revision 834ef79 IE Preview Revisions using System Reflection using System Runtime CompilerServices General Information about an assembly is controlled through the following set of attributes Change these attribute values to modify the information associated with an assembly assembly AssemblyTitle assembly AssemblyDescription assembly AssemblyConfiguration assembly AssemblyCompany assembly AssemblyProduct assembly AssemblyCopyright assembly AssemblyTrademark assembly AssemblyCulture 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 lo
22. g message for the commit and a tab that shows any artifact associations Throughout SpiraTeam revisions are indicated by the icon Source Code File Assemblylnfo cs File Path SampleTestSuite Assemblyinfo cs E File Type Size CH Source amp 2426 KB Last Edited 10 7 2015 4 29 25 PM Author Adam Sandman Latest Revision A 834ef79 Preview Revisions gt Refresh Apply Filter Clear Filter E A 3346879 Adam Sandman Updated the version number 7 Oct 2015 No No T amp 297221 Adam Sandman adding code T Oct 2015 No No Show rows per page i 4 Displaying page 7 of 1 gt gt By clicking on a revision in SpiraTeam you will be taken to the revision details page lt lt Back to Revision List bs Current Branch b master 4 Assemblylnfo cs 834ef79 Source Code Revision 4 834ef79 Py e97f2e1 Notes Updated the version number Edited By Adam Sandman Content A No Build Properties A No Last Edited 10 7 2015 4 29 25 PM Files Associations gt Refresh Apply Filter Clear Filter E Assemblyinfo cs 2426 KB Adam Sandman 834ef79 Modified 7 Oct 2015 Show rows per page i4 lt Displaying page Fa of 1 gt gt i 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 d
23. ionsystem Trunk Commit TortoiseSVN gt S oe Commit to https svn6 taravault net inflectratest3 libraryinformationsystem svn Trunk Message A new version of TortoiseSVN is available Please go to http tortoisesvn net to get it Updated version numbex Changes made double click on file for diff Check All None Non versioned Versioned Added Deleted Modified Files Directories Path Extension Status Property status Lock a SampleTestSuite AssemblyInfo cs cS modified Show unversioned files 1 files selected 1 files total 4 Show externals from different repositories Keep locks C Keep changelsts Lox Click OK and the change known as a revision will now be committed into TaraVault 4 4 Branching and Tagging Now that we have the primary development line in our Trunk we can branch and tag a specific version of the code before we make other changes For example we might be releasing a version and then making changes specific only to the next version We shall create both a branch and a tag from the current Trunk Firstly to create a Branch right click on Trunk and choose TortoiseSVN gt Branch Tag Repository From WC URL tos svn6 taravault net inflectratest3 lbrar yi To path Trunk Destination URL https svn6 taravault net inflectratest3 librar yinformationsystem svn Trunk Log message Create copy in the repository from HEAD revision in the r
24. is is normal it means simply that the source code viewer is initializing for initial use Whenever you access a TaraVault project for the first time you will see this After a few minutes it will be ready for use and you can refresh the page to display Repository Browser Refresh Refresh if Flher r Current Branch jj master T Root Ei SampleTestSuite Fl SeleniumSampleTast Displaying 1 2 out of 2 file s in the current folder Root Filenan To d Edited a F room om Pao capeta Tike m a a ET J pii 1 2560 KB Adam Sandman TDet 2D15 4836 KB Adam Sandman Padet 2005 Show 15 F rows por page ai Displaying page hi mo tem 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 Current Branch b master r the current folder To view the file details click on a file hyperlink the main source code file grid 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
25. it dialog box 4 C Temp Git sampleapplicationone SeleniumSampleTest Commit Tortois ole ee Commit to experimental new branch Message updated code to use newer api Amend Last Commit Set commit date Set author Add Signed off by Changes made double click on file for diff Check All None Unversioned Versioned Added Deleted Modified Files Submodules Path A SeleniumSampleTest GoogleTest cs a E Show Unversioned Files 1 files selected 1 files total Do not autoselect submodules View Patch gt gt Whole Project Message only Enter in a comment in the Message text box that describes the purpose of the change Then click OK On the success dialog box that appears click Close Now unlike other VCS such as Subversion we have made all of these changes in the local Git repository Once you are ready to share your changes with your team you need to Push the local branches to the remote TaraVault repository To do this right click on the top level folder sampleapplicationone and choose TortoiseGit gt Push The following dialog box will be displayed 43 C Temp Git sampleapplicationone Push TortoiseGit Ref Push all branches Local experimental Remote Destination Remote Arbitrary URL Options Force Overwrite Existing Branch May discard changes Use Thin Pack For slow network connections Indude Tags Autolo
26. lease click on the Edit link next to his her name To create a new user either click on the Add button or choose the option to Import from an LDAP server To see any pending new user requests click on the Pending Requests item in the left hand navigation FirstName AY MIAV LastName 4 UserName AY Admin AY Co Co J C Amy Cribbins amycribbins No Bernard Tyler bernardtyler No donnaharkness No Software Engineering fredbloggs No QA henrycooper No Email AY Department AY User AY Active AY Operations Oo us No Software Engineering US000013 US000011 No US000006 US000002 US000012 US000007 US000003 US000010 US000005 US000004 m 2 m o Software Engineering Donna Harkness m a Fred Bloggs m 2 Henry Cooper Jack Van Stanten Joe Smith Martha Noble Ricky Pond Roger Ramjet m 2 Software Engineering jackvanstanten No Software Engineering joesmith No QA marthanoble No rickypond No rogerramjet No m 2 m Q Software Engineering m Q Software Engineering m 2 Software Engineering Rory Rose System Jones Smith Administrator roryjones rosesmith administrator Software Engineering Software Engineering US000009 US000008 US000001 m 2 m a VIVIVIVIVIVIVIVIVIVIVvVIVvVIY m Q m 2 This will display the user details page On this page if you have activated TaraVault there will be a special TaraVault tab that is used to enable a specific
27. lication Two v Planning Testing Tracking Reporting Eu Administrator Administration gt View Edit Projects Y Projects View Edit Projects gt View Edit Projects gt Edit Project Groups The following projects have been created in the system To edit an existing project please click on the Edit link gt Project History Changes To create a new project click on the Add button gt Data Tools w gy PP o EN ME eR gt Custom Properties Legacy Application External Projects 1 Dec 2005 No PR000004 gt Select Edit Copy Delete Library Information System Internal Projects 1 Dec 2005 Yes PR000001 gt Select Edit Copy Delete Sample Application One Internal Projects 1 Dec 2005 Yes PR000002 gt Select Edit Copy Delete gt Requirements Sample Application Two External Projects 1 Dec 2005 Yes PR000003 gt Select Edit Copy Delete gt Planning Fiter ada Clear Fitter gt Notifications gt Incidents gt Documents gt System v Integration gt TaraVault gt Data Synchronization gt Test Automation gt Add Ons amp Downloads You should see the TaraVault menu entry under the Integration heading If you don t see this option then you might either be self hosted or running SpiraTest If you are running SpiraTest please contact Inflectra customer services to get your account upgraded to Spi
28. minutes it will be ready for use and you can refresh the page to display Reposttory Browser Refresh Refresh YY Filter v Current Branch gt Trunk v Displaying 1 0 out of O file s in the current folder b Branches 2 0 0 0 EE J Tagsiv1 0 0 0 E g Trunk TaraVaultProvider show 15 rows per page amp SampleTestSuite Other Operations 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 HEAD revision of the repository Also note that the page will display the folders and files for the currently selected branch in the example above Trunk you can change the current branch at any time by selecting it from the dropdown menu Current Branch fe Trunk fr the current folder b Branches v2 0 0 0 ib Taqsiv1 0 0 0 The file grid 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 can filter and sort on any of the columns as well Displaying 1 5 out of 5 file s in the current folder SampleTestSuite ov FilenameAY O OO TT TT E o o i OSES Lo JL E m 4 Assemblylnfo cs 2426 KB administrator taravault net 7 Oct 2015 7 Oct 2015 7 Oct 2015 7 Oct 2015 E SampleTestSuite nunit 189 KB administrator Dtaravault net 7 Oct 2015 Show rows per page i 4 Displaying pag
29. nfiguration http localhost SpiraTest fredbloggs fredbloggs 1 1 2 SpiraTestConfigura public class SampleTestFixture 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 A icon Preview Revisions gt Refresh Filter Clear Filter RE uai A o O 1 ot J E any v v any v v E A 2 administrator taravault net adding code 7 Oct 2015 No No Show 15 Y rows per page M 4 Displaying page E of 1 gt PI By clicking on a revision in SpiraTeam you will be taken to the revision details page lt lt Back to Revision List af Current Branch b Trunk SampleTestFixture cs A2 Source Code Revision 2 Notes adding code Edited By administrator taravault net Content A No Build Properties A No Last Edited 10 7 2015 12 43 21 PM Files Associations gt Refresh Apply Filter Clear Filter oV FilenameAY SizeAY Author AY Latest Revision AY Action AY Last Edited AY C O M a a ES Assemblyinfo cs 2426 KB administrator Dtaravault net Added 7 Oct 2015 Added 7 Oct 2015 Added T Oct 2015 Added 7 Oct 2015 Added 7 Oct 2015 a Assemblylnfo cs 2426 KB administrator tar
30. nto Bare Repo T No Checkout F Branch J origin Name Load PuttyKkey yy m From SVN Repository T From SVN Repository Trunk trunk Tags tags Branch branches From 0 Username x l ce J Heo You need to enter the following e URL needs to be the TaraVault Git connection string listed under My Profile for the current project e Directory needs to be the local name of the folder for the local repository Typically it is best to make it the same as the name of the project in TaraVault e g C Temp Git libraryinformationsystem in this example When you click on the OK button the following authentication dialog box will appear ee TortoiseGit git CU stdin wrapper mii Username for https git6 taravault net kdministrator taravault net TortoiseGit git CU stdin wrapper Password for https administrator taravault net gits taravault net LET ETL et Enter your TaraVault password and then click OK again The success dialog will appear C Temp Git Git Command Progress TortoiseGit Cloning into C NTempiCitisampleapplicationone warning You appear to have cloned an empty repository Checking connectivity done Success 66628 ms 10 7 2015 4 16 32 PM You will now get a folder c Temp Git sampleapplicationone that is completely empty apart from a special git folder that is used by Git internally Now that you have your Git l
31. ocal repository and working folder available you are ready to start using Git 5 4 Adding Files to the Master Branch Now that you have your Git repository ready we shall simulate working on a real project You can now copy some code and folders into the empty working folder which will be set to use the master branch In this example we shall add some sample Inflectra code git 10 7 2015 4 16 PM File folder SampleTestSuite 10 7 2015 4 20 PM File folder SeleniumSampleT est 10 7 2015 4 20 PM File folder xa SpiraTestWUnitAddin sin 10 3 2014 2 29 PM Microsoft Visual 5 UpgradeLog XML 10 3 2014 2 29 PM AML File Select all the files and folders and choose TortoiseGit gt Add That will display the following dialog box ge CA Temp Git sampleapplicationone Add TortoiseGit Path Not Versioned Files ct SampleTestSuite AssemblyInfo cs cE SampleTestSuite SampleTestFixture cs ez SampleTestSuite SampleTestSuite csproj Ba Sample TestSuite Sample TestSuite csproj user Hu SampleTestSuite SampleTestSuite nunit E SeleniumSampleTest AssemblyInto cs ct SeleniumSampleTest GoogleTest cs ez SeleniumSampleTest SeleniumSampleTest csproj PA SeleniumSampleTest SeleniumSampleTest csproj user Indude ignored files Ee ee ES Select all the files and click OK 43 Add Finished Action Path Added SampleTestSuite SampleTestSuite csproj user Added SampleTestSuite SampleTestSuite nunit Added SeleniumSampleTest A
32. of project source code files and revisions TaraVault is provisic You can change which users are active for source code management in the View Edit Users screen TaraVault Global Settings Available TaraVault Users 5 1 View List inflectratest3 117326 Active TaraVault Users TaraVault Account Name TaraVault Project Settings Source Control project created TaraVault Project Active Yes TaraVault Project Name libraryinformationsystem Subversion https svn6 taravault net inflectratest3 libraryinformationsystem svn TaraVault Project Type Client Connection Users assigned to this project system Administrator administrator administrator Edit Users The system will then populate the Client Connection section with the URL that you need to use to connect to this TaraVault project from your Subversion or Git client this is described in more detail in sections 4 and 5 respectively In addition it will display a list of users that are enabled for this project 3 2 Managing Users By default the built in system administrator account will be automatically enabled for TaraVault use and will be added as a member of all TaraVault projects To enable other users to commit code files to a TaraVault repository you need to go to the Administration gt Users gt View Edit Users menu item View Edit Users import Users From an LDAP Server The following approved users exist in the system To edit an existing user p
33. oned at least one Git project in TaraVault following the steps in section 2 and 3 So you should now have a TaraVault user password and a Git project with a connection URL Passwords amp Security Email Preferences LDAP Settings TaraVault Connection Regional Settings Actions User Login administrator taravault net Project Connection https git6 taravault_net inflectratest3 sampleapplicationone git User Password 56310dc45e0 The next step is to actually connect to this repository using a Git client and commit some source code We recommend using a GUI tool such as TortoiseGit but you can use any standard Git client with TaraVault command line or GUI based just as well In our examples we shall be using TortoiseGit The first thing we need to do is perform an initial clone of our remote Git repository into a local repository This will also do an implicit checkout from the local repository into the working directory Assuming that you have already installed TortoiseGit you would now create a folder to hold all of your Git projects in our example we shall use c Temp cit and right click and choose Git Clone al Git Clone 7 Git Create repository here RE TortoiseGit The following dialog box will appear amp Git clone TortoiseGit Clone Existing Repository URL git6 taravault net inflectratest3 sampleapplicationone ait v Directory C Temp Git sampleapplicationone depth 0 Recursive Clone i
34. op of it rather than simply a VCS Another major difference between Git and Subversion is that Git has built in support for branches instead of relying on a specific folder structure In Git Branches are used to develop features isolated from each other The master branch is the default branch when you create a repository You can then use other branches for development and merge them back to the master branch upon completion 5 2 Working with Remotes To be able to work on any Git project you need to know how to manage your remote repositories Remote repositories the versions of your project that are hosted TaraVault itself Collaborating with others involves managing these remote repositories and pushing and pulling data to and from them when you need to share work Managing remote repositories includes knowing how to add remote repositories remove remotes that are no longer valid manage various remote branches and define them as being tracked or not and more This is in stark contrast to Subversion described in section 4 where every commit and update is being performed directly on the central TaraVault remote repository So when you make changes to your local repository the will need to explicitly synchronized with TaraVault for other users to see them and for them to appear in Spira Local Remote working staging directory area 5 3 Getting Started with Git This section assumes that you have already provisi
35. raTeam Click on this TaraVault link to bring up the TaraVault administration home page TaraVault Configuration Sample Application Two Change Project TaraVault is the hosted source code repository and software configuration management SCM system provided by Inflectra Projects in SpiraTeam can be enabled in TaraVault for storage of project source code files and revisions TaraVault is provisioned based on a specific number of active users across all projects You can change which users are active for source code management in the View Edit Users screen This screen lets you know that your instance of Spira does not yet have an active instance of TaraVault This is normal and you should now click on the Activate TaraVault button to activate TaraVault Once this is done the screen will display TaraVault Configuration Sample Application Two Change Project TaraVault is the hosted source code repository and software configuration management SCM system provided by Inflectra Projects in SpiraTeam can be enabled in TaraVault for storage of project source code files and revisions TaraVault is provisione You can change which users are active for source code management in the View Edit Users screen TaraVault Global Settings Available TaraVault Users 5 Active TaraVault Users 1 View List TaraVault Account Name inflectratest3 117326 TaraVault Project Settings TaraVault Project Active No TaraVault Project Typ
36. red 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
37. sion project in TaraVault following the steps in section 2 and 3 So you should now have a TaraVault user password and a Subversion project with a connection URL Passwords amp Security Email Preferences LDAP Settings TaraVault Connection Regional Settings User Login administrator taravault net Project Connection https svn6 taravault net inflectratest3 libraryinformationsystem svn User Password Click to show password The next step is to actually connect to this repository using a Subversion client and commit some source code We recommend using a GUI tool such as TortoiseSVN but you can use any standard Subversion client with TaraVault command line or GUI based just as well In our examples we shall be using TortoiseSVN The first thing we need to do is perform an initial check out of our repository into a new working folder that will initially be empty Assuming that you have already installed TortoiseSVN you would now create a folder to hold all of your Subversion projects in our example we shall use c Temp Subversion and right click and choose TortoiseSVN gt Check Out we SVN Checkout TortoiseSVN The following dialog box will appear amp Checkout Repository URL of repository ittps svn taravault net inflectratest3 libraryinformationsystem svn Y m Checkout directory Temp Subversion libraryinformationsystem Multiple independent working copies
38. source code repository to each user s workstation 5 1 Git Basics The major difference between Git and most other VCS e g Subversion described in the previous section is the way Git thinks about its data Conceptually most other systems store information as a list of file based changes These systems CVS Subversion Perforce Bazaar and so on think of the information they keep as a set of files and the changes made to each file over time Checkins Over Time ee on File A Al A2 Fite 5 oath A1 pi A2 File Ce A1 A2 e A3 Git doesn t think of or store its data this way Instead Git thinks of its data more like a set of snapshots of a miniature filesystem Every time you commit or save the state of your project in Git it basically takes a picture of what all your files look like at that moment and stores a reference to that snapshot To be efficient if files have not changed Git doesn t store the file again just a link to the previous identical file it has already stored Git thinks about its data more like a stream of snapshots Checkins Over Time Version 1 Version 4 File A File B B1 B2 Doo TO TO File C C2 c3 This is an important distinction between Git and nearly all other VCSs It makes Git reconsider almost every aspect of version control that most other systems copied from the previous generation This makes Git more like a mini filesystem with some incredibly powerful tools built on t
39. ssemblyInfo cs Added SeleniumSampleTest GoogleTest cs Added SeleniumSampleTest SeleniumSampleTest csproj Added SeleniumSampleTest SeleniumSampleTest csproj user Added SpiraTestNUnitAddIn sin Added UpgradeLog XML Finished Success 405 ms 10 7 2015 4 24 33 PM Click on OK to commit the files to the local repository Note that this does not send them to the remote TaraVault repository at this stage since this is a distributed version control system and all commits are done locally 4 CNTempNGitisampleapplicationone Commit TortoiseGit Commit to master new branch Message adding code Amend Last Commit Set commit date Set author Add Signed off by Changes made double click on file for diff Check All None Unversioned Versioned Added Deleted Modified Files Submodules Path a SampleTestSuite AssemblyInfo cs c SampleTestSuite SampleTestFixture cs E SampleTestSuite SampleTestSuite csproj ra A o o o 4 m Show Unversioned Files 11 files selected 11 files total Do not autoselect submodules View Patch gt gt Whole Project E Message only Enter in the appropriate commit message and then click OK to complete the local commit The following screen will be displayed p 2 C Temp Git sampleapplicationone Git Command Progress Tortoi bo el penso SeleniumSampleTest SeleniumsampleTest csproj user create mode 100644 SpiraTestNUnitAddin sin create mode 100644 UpgradeLog XML Success 234 ms
40. st Add to libraryinformationsystem rar Compress and email Settings Compress to libraryinformationsystem rar and email 4 Help About wo 2 R Combine supported files in Acrobat This will display the following oY C Temp Subversion libraryinformationsyste E ES Path Extension d Branches m Tags di Trunk Select deselect all Enable Auto Properties Once they are added then choose TortoiseSVN gt Commit to commit these folders to the TaraVault repository That will display the following dialog box 4 C Temp Subversion libraryinformationsystem Branches Commit TortoiseSVN Commit to multiple targets selected Message A new version of TortoiseSVN is available Please go to http tortoisesvn net to get it added base layout Changes made double dick on file for diff Check All None Non versioned Versioned Added Deleted Modified Files Directories Extension Status Property status Lock added 7 added m Trunk added q E Show unversioned files 3 files selected 3 files total 4 Show externals from different repositories Keep locks Keep changelists Typically you should add a message to describe what you did Then click OK and the three layout folders will now be added to your TaraVault subversion repository 4 3 Adding Files to the Trunk Now that you have your Subversion repository layout setup we shall simulate working on a real project
41. x and then click the Add button Project Membership Passwords amp Security TaraVault Membership Enable user for TaraVault TaraVault User Login fredbloggs taravault net 234 59 TaraVault User Password nabled for this User i as Operations PR 1 Library Information System Remove Add Projects The user will now be listed for that specific TaraVault project If you now go back to the main Administration gt TaraVault page TaraVault Global Settings Available TaraVault Users 5 Active TaraVault Users 2 View List TaraVault Account Name inflectratest3 11 326 TaraVault Project Settings TaraVault Project Active Yes TaraVault Project Name libra ryinformationsystem TaraVault Project Type Subversion Client Connection https svn6 taravault net inflectratest3 libraryinformationsystem svn Users assigned to this project system Administrator administrator administrator Edit Users Fred Bloggs fredbloggs fredbloggs Edit Users You will see the two users listed under the current project If you click on the Edit Users hyperlink it will let you make changes to the user s TaraVault settings For example you may wish to deactivate a user to free up a TaraVault license for another user Individual users can see their own TaraVault profile from the main Spira profile page They need to click on the My Profile link under their user s avatar on the main Spira navigation page
Download Pdf Manuals
Related Search