SpiraTeam Build Server IntegrationGuide
Contents
1. cvs None 9 Subversion Modules Repository URL svn doctor Common Local module directory optional Check out Strategy Use svn update as much as possible Use sve update whenever possible making the build faster But this causes the artifacts from the previous build to remain when a new build starts Repository browser Auto Save Apoy Build periodically Poll SCM Build Environment Enable Spira integration Build Add build step Y Post build Actions LJ Aggregate downstream test results Archive the artifacts Build other projects Publish JUnit test result report E Publish Javadoc Record fingerprints of files to track usage LJ E mail Notification Under the section Build Environment select the checkbox marked Enable Spira Integration That will display the SpiraTeam configuration panel for this Job Build Environment Enable Spira Integration Spira Configuration Project ID 1 Release Version Number 1 0 0 0 Venfy Release Now you need to enter the following values e Project ID The numeric ID of the SpiraTeam Project that the Build belongs to e g for Project PR00001 just enter 1 e Release Version Number The version number of the SpiraTeam Release Iteration that the Build belongs to e g for Release RL0004 with version number 1 0 0 0 you d enter just 1 0 0 0 Once you have entered in the Project ID and Release version number click the Verify Release button and the2. C TeamCity buildAgent temp buildTmp lt br gt agent Publishing internal artifacts br Sending using WebPublishercbr Sending using ArtifactsCachePublisherzbr Checkout directory C TeamCity buildAgent work 217a0c719f7601ef lt br gt checkout Updating sources lt br gt Using vcs information from agent file 217a0c719f7601ef xml br checkout VCS Root svnz doctor Common Test Checkinzbr revision 28919 br Using marlana ona s Feet 4A 7 hel Cant OVA undata in anabloadebhri ft nae situlbulldOtatintiallalus beou htldOtensDureation coureaslleadate unluas A797 0 A Succeeded Creation Date 6 23 2015 2 37 56 PM Last Updated 6 23 2015 2 38 15 PM Incidents Test Runs Show hide columns v an A Any v Inf i4 4 Displaying page a a of 0 gt P Type A Status A Y Priority AY Detected By AV This page will display the status success failure and details of the build imported from the TeamCity Console Output together with a list of the associated incidents test runs and source code revisions The following section will explain how to use your Source Code Management SCM system to take advantage of the SpiraTeam plugin and automatically link incidents and source code revisions to the build information 3 6 Working with Source Code Changesets When your developers commit changes to your application s source into the SCM repository they should make sure to link the commit to the appropriate artif
3. Microsoft Corporation 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
4. each Jenkins project with a corresponding project and release in SpiraTeam Then each time Jenkins creates a new build a new build artifact will be created in SpiraTeam Each build in SpiraTeam will be automatically linked to the incidents fixed source code revisions committed and any SpiraTeam tokens in the Jenkins changelog will be parsed and turned into SpiraTeam artifact hyperlinks 2 2 Installing the SpiraTeam Plug in for Jenkins Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam http www inflectra com Spira Team Downloads aspx Listed on this page will be the SpiraTeam Plug In for Jenkins Right click on this link and save the Zip compressed folder to a temporary location Open up the compressed folder and extract the spira plugin hpi file contained inside Now open up a web browser and connect to your Jenkins server Last Success Last Failure Last Duration 1 day 15 hr 257 1 day 16 hr 255 Build Queue No builds in the queue Build Executor Status Status 1 idle 2 Idle Click on the Manage Jenkins hyperlink following by the Manage Plugins hyperlink That will bring up the page that displays all the currently loaded plugins Click on the Advanced tab Jenkins Plugin Manager 4 Back to Dashboard Updates Available Installed Advanced 7 Manage Jenkins HTTP Proxy Configuration Server Port User name Password No Proxy Host Submit Uplo
5. plugin will connect to SpiraTeam and verify that the project exists that the current user can connect to that project and that the specified release iteration exists in the project Once it has verified successfully click the Save button at the bottom of the screen to save your Job configuration settings You are now ready to use Jenkins with SpiraTeam 2 5 Viewing the Build Results in Spira Team Now that you have associated your Jenkins job with a specific SpiraTeam project and release iteration you can now use Jenkins to manage your software builds and have the results of the build be reported back into SpiraTeam For example when the Build JUnit job illustrated in the previous section is executed it will report back the following result in Jenkins S Ww Name Last Success Last Failure Last Duration wW 3 Build JUnit 1 day 18 hr 97 1 day 18 hr 95 0 87 sec 3 Icon SML Legend EJ RSS for all EJ RSS for failures EJ RSS for just latest builds The corresponding build entry will also be created in SpiraTeam under the specified project and release iteration Incidents Regs amp Tasks Test Cases Comments Custom Props Test Runs Build Name AY Creation Date AV Pod B F Build JUnit 97 14 Mar 2012 BL000045 gn A Nlar 2 Pin T 14 Mar 2012 BL000044 Build JUnit 97 Succeeded Started by user anonymous Building in workspace D Program FilesWenkins jobs Build 14 Mar 2012 BL000043 3 JUnit workspace Upda
6. 15 11 18 30 AM TRAPS P2015 11 11 15 AM TP1 P1 54 T2015 4 33 11 PM TE1 F1 63 7 7 2016 3 26 52 PM Clicking on either of the hyperlinks will allow you to navigate to the Build details page inside SpiraTeam o Default Group v gt TeamCity Test Project v Search Planning Testing Tracking Reporting LE Bloggs v Releases gt Build Details lt lt Back To Build List Build 9 TP1 P1 68 BL 000103 d Release 1 0 Name TP1 P1 68 gTP1 P1 68 E Description Information retrieved from Bamboo br Manual run by lt a hrefz http localhost S08S browse user brgruber Bruno Grubers a gt lt br gt of TR1 P1 68 lt br gt gj TP1 P1 56 E TEE RT RSs Ma oa VALE 7 at 2015 07 08 14 21 40 675 lt br gt with duration of 2267 miliseconds lt br gt ManualBuildTriggerReason userName brgruber m TP1 P1 865 dependenciesDisabled false lt br gt amp TP1 P1 54 amp TP1 P1 53 83 TP1 P1 52 8 TP1 P1 651 8 amp 8 TP1 P1 50 8 TP1 P1 59 Status Creation Date 7 8 2015 2 21 40 PM amp TP1 P1 58 amp TP1 P1 57 Last Updated 7 8 2015 2 21 46 PM 83 TP1 P1 56 bad TP1 P1 55 8 TP1 P1 54 gt Refresh Apply Filter Clear Filter TP1 P1 53 a ET aT z E SS i EFU z G m v Revision AY Author A Y Summary AY Commit Date AV Content A AY Properties A AV 83TP1 P1 52 8 TP1 P1 51 Of D CO mI an v w v 8 TestProject2 SDK compiler ste Show 15 w rows per page 4 4 Displaying page iN of P P 81 Project 1 BuildConfigTe
7. 18 BL 000117 BL 000116 BL 000115 If you have configured your Project Home to include the list of recent builds the build information will also be displayed on the Project Home dashboard Recent Builds Creation Date Project 1 amp ConsoleApplication1 B 20150 28 3 Suc caede d 7 7 20 2015 11 50 46 AM Wj Project01 ConsoleApplication1 B 20150728 8 1 28 2015 11 35 02 AM Project 1 amp ConsoleApplication1 B 20150728 7 28 2015 11 35 07 AM Project 1 amp ConsoleApplication1 B 20150728 6 7 28 2015 11 19 16 AM T 28 2015 11 15 56 AM 7 Project01 amp ConsoleApplication1 B 20150728 5 Succeeded Name Status o v Default Group v gt TeamCity Test Project v Searc Planning Testing Tracking Reporting LE Bloggs Releases gt Build Details Build 9 ProjectO1 amp ConsoleApplicationi B 20150728 9 BL 000122 Name Project01 ConsoleApplication B 20150728 9 Back To Build List 8 Release 1 0 amp Project01 ConsoleApplication1 8 Project01 amp ConsoleApplication1 8 Project01 ConsoleApplication1_ soft VisualStudio Services Identity IdentityDescriptor System String lt br gt and project collection DefaultCollection lt br gt for Project01 a ConsoleApplication1 B 20150728 9 br with URL http vm Description Information retrieved from TFS Build requested by bruno gruber lt br gt from Team System Ling Enumerable lt Joinlterator gt d__61 4 Microsoft TeamFoundation Server Core Team
8. A007 ee NE Wee e spiraTeam spiraPlan AU spiralest SS SpiraTeam Build Server Integration Guide Inflectra Corporation Date July 30th 2015 inflectra Contents 1 Introduction opiraTeamQ is an integrated 1 Introduction eeeeeee 1 Application Lifecycle Management ALM system that manages your 2 Integrating with Jenkins Hudson 2 project s requirements releases test cases issues and tasks in one unified 3 Integrating with Teamc City 9 environment 4 Integrating with Bamboo ee 16 Spira Team 6 contains all of ne features provided by SpiraTest our 5 Integrating with Team Foundation Server 22 highly acclaimed test management system and SpiraPlan our agile project management solution With integrated customizable dashboards of key project information SpiraTeam amp allows you to take control of your entire project lifecycle and synchronize the hitherto separate worlds of development and testing opiraTeamQ includes the ability to integrate with a variety of continuous integration automated build servers so that the results of automated builds can be displayed in SpiraTeam linked to the associated release or iteration In addition the results of automated tests and source code operations can be linked to the build events providing traceability from a specific build to the bugs that were fixed t
9. D 000 0 0 000 oO Bug Bug Bug Bug Bug Bug Bug Incident Bug Bug Bug Bug Bug Incident Incident New New New Assigned New New Assigned New New New New Assigned New New New System Administrator Fred Bloggs Fred Bloggs System Administrator System Administrator Fred Bloggs Fred Bloggs System Administrator Fred Bloggs Fred Bloggs Fred Bloggs System Administrator System Administrator Fred Bloggs Fred Bloggs 12 Jun 2015 1 Jun 2015 28 May 2015 14 May 2015 13 May 2015 8 May 2015 5 May 2015 29 Apr 2015 21 Apr 2015 16 Apr 2015 15 Apr 2015 13 Apr 2015 13 Apr 2015 31 Mar 2015 31 Mar 2015 Build 0004 Joe P Smith Build 0004 Joe P Smith Fred Bloggs Congratulations You are now able to use SpiraTeam and TeamCity to be able to manage your builds and have the build status integrated into your SpiraTeam project dashboard 4 Integrating with Bamboo This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the Atlassian s Bamboo continuous integration build servers It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v4 0 or later and a working installation of Bamboo v 5 0 or later If you have an earlier version of SpiraTeam you will need to upgrade to at least v4 0 4 1 Overview Bamboo provides continuous
10. FoundationT eam Microsoft TeamFoundation Server Core_TeamFoundationTeam Micro 8 Project01 ConsoleApplication1 SEC s2013 8080 tfs DefaultCollection Project01 build buildUri vstfs Build Build 104 amp a summary lt br gt located at lt br gt Build Started at 7 28 2015 Project01 amp ConsoleApplication1 tfs2013 808 j T y 4 in 3 50 46 PM lt br gt Build finished at 7 28 2015 3 50 58 PM lt br gt Status Succeeded 3 Project01 ConsoleApplication1 3 Project01 Build01 20150728 6 3 Project01 Build01 20150728 1 8 Project01 ConsoleApplication1_ 8 Project01 ConsoleApplication1_ Project01 ConsoleApplication1_ 8 Project01 Buildd1_20150724 2 8 Project01 amp ConsoleApplication 3 Project01 Build01_20150724 1 3 Project01 amp ConsoleApplication1 83 Project01 ConsoleApplication1 z 8 TP1 P1 269 v WU Name 4 iype AV tatus A Priority sic ted By reation Date 8 TP1 P1 268 Any v Any v Any Y Any v 8 TP1 P1 66 p 8 TP1 P1 65 Show 15 v rows per page 81 TP1 P1 64 Status Succeeded Creation Date 7 28 2015 11 50 46 AM Last Updated 7 28 2015 11 51 05 AM Associations Revisions Incidents Test Runs gt Refresh Apply Filter Clear Filter Show hide columns v Displaying 1 0 out of 0 incident s in the current build Filtering results by Build Clear Filters j l M Owner 4 Progress DAY Any Y Any v IN 14 4 Dis
11. Relay SpiraTeam textId slacktext lt botSettings gt lt f Please enter the information related to the SpiraTeam Project you want to associate with TFS bellow For detailed information please check the manual gt lt add name spiraURL value http doctor SpiraTeam lt The URL of SpiraTeam gt lt add name spiraUser value username gt The user name of SpiraTeam gt lt add name spiraPassw value P ssword gt lt The password of SpiraTeam gt lt add name spiraPnumber value 8 lt The number of the SpiraTeam project gt add name spiraPvers value 1 0 0 0 gt lt The Release version of the SpiraTeam project gt lt botSettings gt lt eventRules gt rule notify true events BuildCompleted teamProjectCollection lt eventRules gt lt bot gt areaPath teamProject TFSProject 1 teamName gitRepository lt I 0E EC ke ce cie e cie cie cie cie cie cie cie cie cie che cic ce cic cie cic cie cic che cic clie cic cie cic cic clc cic cic clie ce cie cic aic clc cic cie aic che cic cie cic clic cic cic cie chc cic clie cic clic cie cie cc cie cc cic cie cic chc cic cle cic cie cic ce cic chc cic cle cic cie cic cie clc cic cic cie clc cie cic cic clie cic cic afe chic cic cie cic cie cic cic cic cie cic cic cde cic cde cie cc cic ce cic cie cic che cic ce cic ce cic ci cic cl cic cle cic cie cic oe cic cie cc oe cie oC oe OC XX E bot id spira2 typ
12. Smith 1 Nov 2003 1 Nov 2003 1 Nov 2003 2 Nov 2003 2 Nov 2003 2 Nov 2003 4 Nov 2003 4 Nov 2003 4 Nov 2003 4 Nov 2003 15 Nov 2003 15 Nov 2003 15 Nov 2003 15 Nov 2003 15 Nov 2003 Joe P Smith Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith Build JUnit 92 Build JUnit 92 Build 0001 Build 0001 Build 0002 Build 0002 Build JUnit 97 Build 0004 Build 0004 Build 0005 Build 0005 Build 0005 Build 0005 i4 Displaying page 1 Jof NO IN000001 IN000002 IN000003 IN000004 IN000005 IN000006 IN000007 IN000008 IN000009 IN000010 IN000011 IN000012 IN000013 IN000014 IN000015 3 Integrating with TeamCity This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the JetBrains TeamCity continuous integration build servers It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v4 0 or later and a working installation of TeamCity v9 0 4 or later If you have an earlier version of SpiraTeam you will need to upgrade to at least v4 0 3 1 Overview TeamCity provides continuous integration services for software development primarily in the Java programming language It is a server based system running that supports a variety of different version control systems and build runners It supports SCM tools including CVS Subversion Git Mercurial Perfor
13. TestProject 1 illustrated in the figure bellow is executed it will report in Bamboo a E Bamboo MyBamboo Build Deploy Reports Create a O A M Build projects TestProject1 Plan1 Build 68 Demonstrating SpiraTeam Add on features 00000000009 Run Actions 2 68 was successful Manual run Build summary Tests Commits Artifacts Logs Metadata Build result summary Details Included in deployment project Completed 08 Jul 2015 2 21 43 PM 1 hour ago TestProject2 Duration lt 1 second No release with the artifacts of this build exists yet Labels None Create release Show more Write a comment The corresponding build entry will also be created in SpiraTeam under the specified project and release iteration Builds gt Refresh Apply Filter Clear Filter Displaying 1 15 out of 43 build s in this release iteration Build Name A Creation i Status 1 E 1P1 P1 68 amp TP1 P1 66 9 1P1 P1 65 F 1P1 P1 64 68 Jul 2015 68 Jul 2015 8 Jul 2015 7 Jul 2015 8 Jul 2015 8 Jul 2015 8 Jul 2015 7 Juk2015 7 Jul 2015 BL 000103 BL 00D101 BL 000100 BL 000097 F 1P1 P1 263 7 Jul 2015 BL ODOD96 If you have configured your Project Home to include the list of recent builds the build information will also be displayed on the Project Home dashboard Recent Builds Name Creation Date TP1 P1 468 2 8 2018 2 21 40 PM TE1 P1 56 7 8 20
14. acts in SpiraTeam For example they may want to record that the revision fixes a specific incident or implements a specific feature requirement Linking an artifact is very simple All the developer needs to do is enter the artifact token in the following format PREFI X I D 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 requirements identifier is RQ Incidents are IN and tasks are TK The artifact ID is the number of the artifact So by creating a commit message that reads Due to requirement RQ 12 the code for toString in class XML parser was modified This also fixed Incident IN 1034 SpiraTeam will automatically detect the tokens and will include links to them under the Associations tab for each revision detail in SpiraTeam Inside SpiraTeam the system will use the same information to automatically link the list of associated revisions to the build record Associations Revisions Incidents Test Runs gt Refresh Apply Filter Clear Filter O 428796 bgruber Show 15 Y rows per page 4 4 Displaying page 1 of 1 gt If the commit message contains Incident tokens the plugin will also automatically link those incidents to the appropriate build Associations Revisions Incidents Test Runs 10 Jun 2015 W this is a test bu
15. ad Plugin You can upload a hpi file to install a plugin from outside the central plugin repository File Upload Update Site URL htto updates jenkins ci org update center json Submit Now you can click on the Browse button next to the section that lets you upload a new plugin to the server Navigate to where you saved the spira plugin hpi plugin file and upload the SpiraTeam plugin into Jenkins Once that has completed click on the Installed tab to display the list of installed plugins Jenlons Plugin Manager Ei Back to Dashboard Updates Available Installed Advanced Enabled i Version Previously installed version Pinned Manage Jenkins 9 CVS Plugin Integrates Jenkins with CVS version contr J Maven Integration plugin y Jenkins SSH Slaves plugin Vj Subversion Plugin 7 Jenkins Translation Assistance plugin Changes will take effect when you restart Jenkins Raster Once No Jobs Ars Running You will see an option to Restart Jenkins and load any recently added plugins Click on this button and Jenkins will automatically restart once all pending jobs have been completed Once Jenkins has restarted you will now see the SpiraTeam plugin listed as one of the installed plugins Jenlons Plugm Manager c Back to Dashboard Updates Available Installed Advanced Manage Jenkins Man nkin CVS Plugin Maven In ration plugi Spira Plugin Plugin for Jenk Jenkins SSH Slaves plugin 2 3 Setting Up
16. am Add a new notification Add build notification Event All Builds Completed iv Notification sent for every fully completed build iv Recipient type SpiraTeam URL hittp doctor SpiraTeam User Name Password Project ID fredbloggs 8 Release Version After that you will see some new fields to fill they are e URL tis the URL you use to access your instance of SpiraTeam e User Name Your SpiraTeam user name e Password Your SpiraTeam password e Project ID The numeric ID of the SpiraTeam Project that the Build belongs to e g for Project PR00001 just enter 1 e Release Version Number The version number of the SpiraTeam Release Iteration that the Build belongs to e g for Release RL0004 with version number 1 0 0 0 you d enter just 1 0 0 0 After filling this boxes with appropriate information click on Aad button Bamboo will then try to connect to the SpiraTeam Server and check the Project Release provided info Once it validates your information the connection settings will be saved In case of error follow the instructions on screen and try again 4 4 Viewing the Build Results in Spira Team Now that you have associated your Bamboo Project and Plan with a specific SpiraTeam project and release iteration you can use Bamboo to manage your software builds and have the results of the build be reported back into SpiraTeam For example when the Plan1 build of
17. ce and Borland StarTeam and can execute Apache Ant and Apache Maven based projects as well as arbitrary shell scripts and Windows batch commands When you use the SpiraTeam Plug In for TeamCity it will allow you to associate each TeamCity project with a corresponding project and release in SpiraTeam Then each time TeamCity creates a new build a new build artifact will be created in SpiraTeam Each build in SpiraTeam will be automatically linked to the incidents fixed tasks implemented requirements developed and source code revisions committed 3 2 Installing the Spira Team Plug in for TeamCity Go to the Inflectra website and open up the page that lists the various downloads available for Spira Team http www inflectra com SpiraTeam Downloads aspx Listed on this page will be the SpiraTeam Plug In for TeamCity Right click on this link and save the Zip compressed folder to the TeamCity s Plug In directory 8T7EAMCITY USER HOME plugins After that restart TeamCity for the plugin to take effect Its also possible to install the Plug In through the user interface of TeamCity via Administration Plugins List Upload Plugin Zip choosing the zip file from your file system T Projects Changes Agents 1 Build Queue o0 Administration Administration Diagnostics Project related Settings Troubleshooting VCS Status Server Logs Internal Properties Logging Presets Caches Search Projects Build Time Browse Data Directory Disk Usag
18. e DevCore TfsNotificationRelay SpiraTeam SpiraNotifier DevCore TfsNotificationRelay SpiraTeam textId slacktext lt botSettings gt lt add name spiraURL value http doctor SpiraTeam gt lt The URL of SpiraTeam gt lt add name spiraUser value username gt The user name of SpiraTeam gt lt add name spiraPassw value P ssword lt The password of SpiraTeam gt lt add name spiraPnumber value 1 lt The number of the SpiraTeam project gt lt add name spiraPvers value 1 0 1 3 gt lt The Release version of the SpiraTeam project gt lt botSettings gt lt eventRules gt rule notify true events BuildCompleted teamProjectCollection lt eventRules gt lt bot gt lt bots gt teamProject TFSProject02 teamName gitRepository areaPath workI Note the differences in spiraPnumber spiraPvers and teamProject fields in the two bots 5 4 Viewing the Build Results in Spira Team Now that you have associated your TFS Project with a specific SpiraTeam project and release iteration you can now use TFS to manage your software builds and have the results of the build be reported back into SpiraTeam For example when the ConsoleApplication1 B build of Project 1 illustrated in the figure bellow is executed it will report in TFS og Visual Studio Team Foundation Server 2013 Project01 HOME CODE WORK BUILD Explorer ao e Muse All build defi
19. e Browse TeamcCity data directory Server Health config Audit Elib Fa plugins User Management Bg Spira zip 148 21 KB Users rms Upload File Groups Pe integrations Path C ProgramData JetBrains TeamCity plugins NuGet Name SpiraTeam Plug In for TeamCity Tools File C Users TeamCity plugin zip Browse Server Administration Global Settings Gance Authentication Email Notifier Jabber Notifier Agent Cloud Diagnostics Backup Projects Import Licenses Clean up Settings Usage Statistics Plugins List Do not forget to restart TeamCity for the plugin to take effect Once TeamCity has restarted you can see the SpiraTeam Plug In listed as one of the installed plugins T e Projects Changes Agents 1 Build Queue o0 Administration Administration gt Plugins List Project related Settings This TeamCity installation has 80 plugins including 1 external Projects Upload plugin zip Available plugins Build Ti External plugins Disk Usage Plugin Name Version Vendor Home Path Server Health Audit Spira Builder Notifier 1 0 0 Inflectra Corporation lt TeamCity Data Directory unpacked Spira 3 3 Setting Up the Spira Team TeamCity Plug in Now that the plugin has been installed you need to configure the Global Settings for integration with SpiraTeam To do this go to Administration Spira Global Settings TC Projects Changes Agents 1 a Build Queue 0 Administration Administra
20. ests that were run and source code files that were modified This guide outlines how to integrate and use SpiraTest SpiraPlan and opiraTeam in conjunction with various build servers commonly used by software development teams This guide assumes that the reader is familiar with both SpiraTeam and the appropriate build server being discussed For information regarding how to use SpiraTeam please refer to the SpiraTeam User Manual 2 Integrating with Jenkins Hudson This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with either the Jenkins or Hudson hereafter referred to as Jenkins continuous integration build servers It assumes that you already have a working installation of SpiraTest SpiraPlan or opiraTeam v3 2 or later and a working installation of Jenkins Hudson v1 405 or later If you have an earlier version of SpiraTeam you will need to upgrade to at least v3 2 2 1 Overview Jenkins provides continuous integration services for software development primarily in the Java programming language It is a server based system running in a servlet container such as Apache Tomcat It supports SCM tools including CVS Subversion Git Mercurial Perforce and Clearcase and can execute Apache Ant and Apache Maven based projects as well as arbitrary shell scripts and Windows batch commands When you use the SpiraTeam plugin for Jenkins it will allow you to associate
21. g Fred Bloggs fixed IN 000092 Incident IN000092 Similarly when you view the list of incidents inside SpiraTeam you will now be able to sort and filter the list by the associated build Internal Projects gt Library Information System Planning Testing Tracking Reporting Incidents dh New Incident 2 Delete Refresh Copy Tools v Y Filter v Displaying 1 15 out of 86 incident s for this project Quick Filter My Filters No filters available Shared Filters Components Administration 3 Author Management 3k Book Management Releases gl Library System Rele ga Library System Rt B iteration 001 B iteration 002 E iteration 003 B Library System Rt Ej iteration 001 E iteration 002 E Iteration 003 gl Library System Rele B Library System Rel B Library System Rel e ltaratinn N14 v O V NmeAY Type AY Ss AY Priory AY Detected By AY Creation Date AV Owner AY Build AV BC LLL o ee Je Em e Y A 2 Database constraint error V this is a bug 2 Rendering issue on author page x Page redirection issue on book list page x Timeout on home page z Bug when displaying book list 2 DNS error when updating author name z bug on aging report 2 Page missing on confirmation screen z timeout bug on submission 2 There is a bug in this screen V Bug in the login page E stem error while changing book genre V pad z incident Show s v rows per page OO 0 DJJEJ DJ E
22. gTest 108 BuildConfigTest 107 BuildConfigTest 105 SDK compiler step 3 BuildConfigTest 104 BuildConfigTest 103 BuildConfigTest 102 BuildConfigTest 101 BuildConfigTest 100 o Name Description Status Associations gt Refresh Apply Filter Clear Filter Displaying 1 0 out of 0 incident s in the current build Filtering results by Build Clear Filters lame AY j IB Creation Date 4 D Jl vMoo Uv UNO NN m Show 15 rows per page Planning Testing Tracking Reporting A Fred Bloggs v Build 9 Project 1 BuildConfigTest 122 BL 000074 Project 1 BuildConfigTest 122 TeamCity server version is 9 0 4 build 32407 lt br gt Build bt1 lt br gt SBUILD_ PROGRESSS Checking for changes lt br gt changesBlock Collecting changes in 1 VCS root lt br gt changesBlock VCS Root details lt br gt svn doctor Common Test_Checkin instance id 1 parent internal id 1 parent L id TestProject_SvnDoctorCommonTestCheckin description svn svn doctor Common Test_Checkin lt br gt Waiting for completion of current operations for the VCS root svn doctor Common Test Checkin br Detecting changes in VCS root svn doctor Common Test Checkin used in BuildConfigTest br 2 Will collect changes for svn doctor Common Test Checkin starting from revision 28924 lt br gt Agent time zone America New_York lt br gt Agent is running under JRE 1 7 0 72 b14 br Clearing temporary directory
23. he Project ID and Release version number click the Save button and the plugin will connect to SpiraTeam and verify that the project exists that the current user can connect to that project and that the specified release iteration exists in the project Once it has verified successfully it will save your Project configuration settings In case of error follow the instructions on screen and try again You are now ready to use TeamCity with SpiraTeam 3 5 Viewing the Build Results in Spira Team Now that you have associated your TeamCity Project with a specific SpiraTeam project and release iteration you can now use TeamCity to manage your software builds and have the results of the build be reported back into SpiraTeam For example when the BuildConfigTest build of Project 1 illustrated in the figure bellow is executed it will report in TeamCity TC Projects Changes Agents 1 Build Queue 0 TeamCity user Administration Hide Successful Configurations Configure Visible Projects v Project 1 Demonstrating SpiraTeam Plug v BuildConfigTest 122 Success lo artifact No change moments ago 17 The corresponding build entry will also release iteration Builds gt Refresh Apply Filter Clear Filter be created in SpiraTeam under the specified project and Displaying 1 15 out of 21 buildis in this release iteration BE hamna Aw build Mame amp YT gm Project 1 BuildConfigTest 122 8j Project 1 BuildC
24. he information related to the SpiraTeam Project you want to associate with TFS bellow For detailed information please check the manual gt lt add name spiraURL value http doctor SpiraTeam lt The URL of SpiraTeam gt lt add name spiraUser value User gt lt The user name of SpiraTeam gt lt add name spiraPassw value P ssword gt lt The password of SpiraTeam gt lt add name spiraPnumber value 8 gt lt The number of the SpiraTeam project gt add name spiraPvers value 1 0 0 0 gt lt The Release version of the SpiraTeam project gt lt botSettings gt lt eventRules gt lt rule notify true events BuildCompleted teamProjectCollection teamProject Project 1 teamName gitRepository areaPath lt eventRules gt lt bot gt lt bots gt If you want to receive notifications from more than one TFS project you will need to create a bot for each TFS project inside the configuration file and associate the TFS project with a SpiraTeam project To do this inside the configuration file copy the whole block from bot to bot Don t forget to associate this new Notificator with a TFS Project entering the TFS project name in the teamProject field After setting up two TFS projects you configuration file should look like this bots bot id spira type DevCore TfsNotificationRelay SpiraTeam SpiraNotifier DevCore TfsNotification
25. he tokens and will include links to them under the Associations tab for each revision detail in SpiraTeam Inside SpiraTeam the system will use the same information to automatically link the list of associated revisions to the build record Associations Revisions gt Refresh Apply Filter Clear Filter Ls Dummies a Deme __ Bonen bee SY Lom T C O 28796 C 4 J BJ fixed IN 000092 bgruber Show rows per page 10 Jun 2015 Yes No i4 lt Displaying page Sa of 1 gt If the commit message contains Incident tokens the add on will also automatically link those incidents to the appropriate build Associations Revisions Incidents Test Runs 10 Jun 2015 W this is a test bug Fred Bloggs fixed IN 000092 Incident IN000092 Similarly when you view the list of incidents inside SpiraTeam you will now be able to sort and filter the list by the associated build S internal Projects kad Incidents dh New Incident 3 Delete gt Library Information System Displaying 1 15 out of 86 incident s for this project Quick Filter My Filters No filters available Shared Filters Components Administration Author Management 3k Book Management Releases El Library System Rele gla Library System Rt B Iteration 001 B iteration 002 B Iteration 003 B Library System Rt Ej iteration 001 E iteration 002 Ej iteration 003 g
26. heck Settings Enter safe mode 4 3 Setting Up the Spira Team Bamboo Add on Now that the add on has been installed you need to configure the settings for integration with opiraTeam To do this go to the Project you want to communicate with SpiraTeam and under the plan you want to receive notifications click on Edit 4 icon In the Plan Configuration screen go to the Notifications tab and click on Add Notification yu t i2Damboo MyBamboo Build Deploy Reports Create Build projects TestProject1 Plan1 Configuration Plan1 00000000009 Run Actions Demonstrating SpiraTeam Add on features Plan Configuration Stages amp jobs 1 Plan details Audit log Stages Repositories Triggers Branches Dependencies X Permissions Notifications Variables Miscellaneous Add notification Default Stage i Job1 w Plan configuration saved successfully Branches 0 Notifications No branches are configured Add one through the configuration You can send notifications to a variety of recipients based on specific build events There is currently no instant messaging server or email server configured Bamboo will not send out any notifications Add an email server or add an instant messaging server now There are currently no notifications set up for this plan In the Add a new notification pop up select the appropriate event you want to receive notifications and in the Recipient type box select SpiraTe
27. ically link those incidents to the appropriate build Revisions Test Runs Show hide columns v niallicessskinser hookhiihe scalas OA aa Joe E Smith 4 1 2003 m P Smith EA JUnit 497 Show 15 v rows per page 4 Displaying Similarly when you view the list of incidents inside SpiraTeam you will now be able to sort and filter the list by the associated build Welcome System Administrator Library Information System v My Profile Administration Log Out Search 19 Help My Page Project Home Planning Testing Tracking Reporting incidents Tasks Resources Source Code Role Project Owner n a spiraTeam dp New Incident 3 Delete Refresh ChCopy ijTools Showmcecounes v Y Filter Displaying 1 15 out of 60 incident s for this project w Cannot log into the application V Not able to add new author V Clicking on link throws fatal error V Database not backing up correctly W cannot install system on Oracle 9i pene Show 15 w rows per page Congratulations You are now able to use SpiraTeam and Jenkins to be able to manage your builds and have the build status integrated into your SpiraTeam project dashboard et Incident New Incident Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Fred S Joe P Smith Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P
28. integration services for software development in any programming language using any build tool It is a server based system running that supports a variety of different version control systems It supports SCM tools including CVS Subversion and Git and can execute Apache Ant and Apache Maven based projects as well as arbitrary shell scripts and Tomcat When you use the SpiraTeam Add on for Bamboo it will allow you to associate each Bamboo project and plan with a corresponding project release in SpiraTeam Then each time Bamboo creates a new build a new build artifact will be created in SpiraTeam Each build in SpiraTeam will be automatically linked to the incidents fixed tasks implemented requirements developed and source code revisions committed 4 2 Installing the SpiraTeam Add on for Bamboo Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam http www inflectra com Spiraleam Downloads aspx Listed on this page will be the SpiraTeam Add on for Bamboo Right click on this link and save the zip file to your local computer Inside this zip file will be a jar file extract the jar file and save to a local folder on your system After that go to Bamboo Administration You will need Bamboo administrator privileges to access this configuration page Under Add ons click on the Manage Add ons link and then on Upload Add on on the left f sBamboo MyBamboo Build Deploy Reports C
29. ith Fred Bloggs Congratulations You are now able to use SpiraTeam and Bamboo to be able to manage your builds and have the build status integrated into your SpiraTeam project dashboard 5 Integrating with Team Foundation Server This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with Microsofts Team Foundation Server hereafter referred to as TFS continuous integration build server module It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v4 0 or later and a working installation of TFS 2013 or TFS 2015 If you have an earlier version of SpiraTeam you will need to upgrade to at least v4 0 5 1 Overview TFS provides tools for managing the entire application lifecycle including source code management reporting automated builds testing and release capabilities for example It supports version control using either its native TFS source code management system or Git SpiraTeam has version control plugins for both TFS native and TFS with Git source code management options When you use the SpiraTeam Build Server Plug In for TFS it will allow you to associate different TFS projects with a corresponding project and release in SpiraTeam Then each time TFS creates a new build a new build artifact will be created in SpiraTeam Each build in SpiraTeam will be automatically linked to the incidents fixed tasks implemented require
30. ject Now that you have setup the Global SpiraTeam and Notifications settings in TeamCity next you need to associate each of your TeamCity Projects with their corresponding SpiraTeam Project and Release Iteration To do this click on the name of a project and then click on the Spira Project Configuration tab for that Project T e Projects Changes Agents 1 Build Queue 0 Administration Project 1 Demonstrating SpiraTeam Plug In for TeamCity Edit Project Settings Overview ChangeLog Statistics CurrentProblems Investigations Muted Problems Spira Project Configuration Spira Configuration Spira URL http localhost SpiraTeam TeamcCity Project ID project Project ID PR 1 Release Version 1 0 0 0 Save In this page you can check the URL of the SpiraTeam Server If it is wrong you can change it in the Spira Global Settings menu see section 3 3 again It is also possible to check the Project ID associated with the project in TeamCity This information can be useful for debugging checking reasons To associate a TeamCity Project with a SpiraTeam Project enter the following values e Project ID The numeric ID of the SpiraTeam Project that the Build belongs to e g for Project PR00001 just enter 1 e Release Version Number The version number of the SpiraTeam Release lteration that the Build belongs to e g for Release RL0004 with version number 1 0 0 0 you d enter just 1 0 0 0 Once you have entered in t
31. la Library System Rele B Library System Rel B Library System Rel w gm ltaratinn nin1 dc In o this is a bug o bug on aging report z Bug in the login page E bad H incident Show rows per page 00 O Dj OOOO 000 0 0 000 Refresh Copy Tools v Y Filter v g 2 Database constraint error g 2 Rendering issue on author page g z Page redirection issue on book list page 8 Timeout on home page Bug when displaying book list g 2 DNS error when updating author name g 2 Page missing on confirmation screen g x timeout bug on submission Ej There is a bug in this screen g E system error while changing book genr Planning Bug Bug Bug Bug Bug Bug Bug Incident Bug Bug Bug Bug Bug Incident Incident Testing E New New New Assigned New New Assigned New New New New Assigned New New New Tracking Reporting i Administrator Fred Bloggs Fred Bloggs System Administrator System pace Fred Bloggs Fred Bloggs System Administrator Fred Bloggs Fred Bloggs Fred Bloggs System nce System Administrator Fred Bloggs Fred Bloggs 12 Jun 2015 1 Jun 2015 28 May 2015 14 May 2015 13 May 2015 8 May 2015 5 May 2015 29 Apr 2015 21 Apr 2015 16 Apr 2015 15 Apr 2015 13 Apr 2015 13 Apr 2015 31 Mar 2015 31 Mar 2015 e Build 0004 Joe P Smith Build 0004 Joe P Sm
32. lude links to them under the Associations tab for each revision detail in SpiraTeam Inside SpiraTeam the system will use the same information to automatically link the list of associated revisions to the build record Associations Revisions Incidents Test Runs gt Refresh Apply Filter Clear Filter O 428796 bgruber Show 15 Y rows per page 4 4 Displaying page 1 of 1 If the commit message contains Incident tokens the plugin will also automatically link those incidents to the appropriate build Associations Revisions Incidents Test Runs 10 Jun 2015 W this is a test bug Fred Bloggs fixed IN 000092 Incident IN000092 Similarly when you view the list of incidents inside SpiraTeam you will now be able to sort and filter the list by the associated build Internal Projects gt Library Information System Planning Testing Tracking Reporting Incidents dh New Incident 2 Delete Refresh Copy Tools v Y Filter v Displaying 1 15 out of 86 incident s for this project Quick Filter My Filters No filters available Shared Filters Components Administration 3 Author Management 3k Book Management Releases gl Library System Rele ga Library System Rt B iteration 001 B iteration 002 E iteration 003 B Library System Rt Ej iteration 001 E iteration 002 E Iteration 003 gl Library System Rele B Library System Rel B Lib
33. ments developed and source code revisions committed 5 2 Installing the SpiraTeam Build Plug in for TFS Go to the Inflectra website and open up the page that lists the various downloads available for Spira Team http www inflectra com SpiraTeam Downloads aspx Listed on this page will be the SpiraTeam Build Plug In for TFS There are two different versions of the plugin for TFS2013 and TFS2015 Select the appropriate version then right click on this link and save the zip file in your system You will need to extract the folder and copy all the files to the TFS Plugins Directory which is usually C Program Files Microsoft Team Foundation Server x x Application Tier Web Services bin Plugins After that TFS will automatically restart and run the SpiraTeam Build Plug In 5 3 Setting Up the SpiraTeam Build Plug in for TFS Once you have copied the SpiraTeam Build Plug In files to the TFS Plugins Directory you will need to configure the plugin To do this you will need to open the file DevCore TfsNotificationRelay dll config using your favorite text editor or Visual Studio for example Then find the section bots and the bot id spira In this section you will input the information related to the SpiraTeam project you want to connect To do this enter the appropriate information in the at each correspondent value field lt add name SpiraURL value Enter your SpiraTeam URL here add name SpiraUser value Enter
34. nitions Queued Completed Deployed My favorites Q Queue build No favorite build definition found a we EE dE 8 6 9 Name Build Definition Build Quality Build01_20150729 1 Build01 Team favorites No team build definition found TAN ConsoleApplication1 B 20150728 9 ConsoleApplication1 B Build definitions x ConsoleApplication1 B 20150728 8 ConsoleApplication1 B All build definitions Buildot ConsoleApplication1 B 20150728 7 ConsoleApplication1 B uildO1 ConsoleApplication1 B 20150728 6 ConsoleApplication1 B ConsoleApplication1 B ConsoleApplication B 20150728 5 ConsoleApplication B ConsoleApplication1 B 20150728 4 ConsoleApplication1 B 00000000 ConsoleApplication1 B 20150728 3 ConsoleApplication1 B The corresponding build entry will also be created in SpiraTeam under the specified project and release iteration v Builds gt Refresh A Filter Clear Filter Displaying 1 15 out of 60 build s in this release iteration F Proiect01 amp ConsoleApplication B 20150728 9 28 Jul 2015 F Project01 ConsoleApplication1 B 20150728 8 28 Jul 2015 F Project01 ConsoleApplication1 B_20150728 7 28 Jul 2015 Project01 amp ConsoleApplicationi B 20150728 6 28 Jul 2015 F Project01 ConsoleApplication1 B 20150728 5 28 Jul 2015 5 Project01 sConsoleApplication B 20150728 4 28 Jul 2015 28 Jul 2015 28 Jul 2015 28 Jul 2015 28 Jul 2015 28 Jul 2015 28 Jul 2015 BL T BL 000122 BL 000120 BL 0001
35. onfigTest 121 TestProject BuildConfigTest 119 te y CJ 23 Jun 2015 BL 000074 23 Jun 2015 BL 000073 19 Jun 2015 BL 000071 23 Jun 2015 23 Jun 2015 19 Jun 2015 If you have configured your Project Home to include the list of recent builds the build information will also be displayed on the Project Home dashboard Recent Builds Hame Project 1 BuildConfigTest 122 Project 1 BuildConfiglest 121 TestProject BuildConfiglest 119 Creation Date 5 23 2015 2 37 56 PM 5 23 2015 2 35 33 PM 5 13 2015 4 01 47 PM Status Clicking on either of the hyperlinks will allow you to navigate to the Build details page inside SpiraTeam y Default Group v gt TeamCity Test Project v it Releases gt Build Details lt lt Back To Build List Release 1 0 F Project 1 BuildConfigTest 122 8 Project 1 BuildConfigTest 121 8j TestProject 8 TestProject S TestProject 8 TestProject BuildConfigTest 119 8 TestProject 8 TestProject 8 TestProject BuildConfigTest 114 BuildConfigTest 113 8 TestProject S TestProject BuildConfigTest 110 8 TestProject 8 TestProject 8 TestProject 8 TestProject 8 TestProject2 8 TestProject S TestProject 8 TestProject 8 TestProject 8 TestProject BuildConfigTest 118 BuildConfigTest 117 BuildConfigTest 115 BuildConfigTest 112 BuildConfigTest 111 BuildConfigTest 109 BuildConfi
36. ow able to use SpiraTeam and TFS to be able to manage your builds and have the build status integrated into your SpiraTeam project dashboard 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 amp SpiraPlan Spira Team and Inflectra are registered trademarks of Inflectra Corporation in the United States of America and other countries Microsoft Windows Explorer and Microsoft Project are registered trademarks of
37. playing page 1 Fa of 0 gt gt i This page will display the status Success failure and details of the build imported from the TFS Console Output together with a list of the associated incidents test runs and source code revisions The following section will explain how to use your Source Code Management SCM system to take advantage of the SpiraTeam plugin and automatically link incidents and source code revisions to the build information 5 6 Working with Source Code Changesets When your developers commit changes to your application s source into the SCM repository they should make sure to link the commit to the appropriate artifacts in SpiraTeam For example they may want to record that the revision fixes a specific incident or implements a specific feature requirement Linking an artifact is very simple All the developer needs to do is enter the artifact token in the following format PREFI X I D 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 requirements identifier is RQ Incidents are IN and tasks are TK The artifact ID is the number of the artifact So by creating a commit message that reads Due to requirement RQ 12 the code for toString in class XML parser was modified This also fixed Incident IN 1034 SpiraTeam will automatically detect the tokens and will inc
38. rary System Rel e ltaratinn N14 v O V NmeAY Type AY Ss AY Priory AY Detected By AY Creation Date AV Owner AY Build AV BC LLL o ee Je Em e Y A 2 Database constraint error V this is a bug 2 Rendering issue on author page x Page redirection issue on book list page x Timeout on home page z Bug when displaying book list 2 DNS error when updating author name z bug on aging report 2 Page missing on confirmation screen z timeout bug on submission 2 There is a bug in this screen V Bug in the login page E stem error while changing book genre V pad z incident Show s v rows per page OO 0 DJJEJ DJ ED 000 0 0 000 oO Bug Bug Bug Bug Bug Bug Bug Incident Bug Bug Bug Bug Bug Incident Incident New New New Assigned New New Assigned New New New New Assigned New New New System Administrator Fred Bloggs Fred Bloggs System Administrator System Administrator Fred Bloggs Fred Bloggs System Administrator Fred Bloggs Fred Bloggs Fred Bloggs System Administrator System Administrator Fred Bloggs Fred Bloggs 12 Jun 2015 1 Jun 2015 28 May 2015 14 May 2015 13 May 2015 8 May 2015 5 May 2015 29 Apr 2015 21 Apr 2015 16 Apr 2015 15 Apr 2015 13 Apr 2015 13 Apr 2015 31 Mar 2015 31 Mar 2015 Build 0004 Joe P Smith Build 0004 Joe P Smith Fred Bloggs Congratulations You are n
39. reate Bamboo administration BUILD RESOURCES Manage add ons Agents Agent matrix You can install update enable and disable add ons here Find new add ons Executables Filter visible add ons User installed Y Upload add on Build a new add on JDKs Server capabilities User installed add ons Global variables Linked repositories ax Shared Credentials Shared credentials Repository settings Audit log Bamboo update check Settings Enter safe mode ELASTIC BAMBOO The Universal Plugin Manager v2 16 2 by Atlassian Configuration he Universal Plugin Manager v2 16 2 by Atl an After that click on Browse and select the jar file extracted from the zip archive downloaded from the Inflectra website Then click on Update After the installation of the SpiraTeam Add on you should see a welcome screen Installed and ready to go SpiraTeam Bamboo Plugin v by Inflectra This add on has been installed If you need help getting started click the link to the add on documentation from the Manage add ons screen You will then be able to see the SpiraTeam Add on in the User Installed Add ons list User installed add ons 4 Shared Credentials v 5 SpiraTeam Bamboo Add on This is the SpiraTeam plugin for Atlassian Bamboo Uninstall Disable No screenshots available Version 1 0 0 3 1 of 1 modules enabled Vendor Inflectra Add on key com inflectra spiratest plugins bamboo Audit log Bamboo update c
40. roughout SpiraTeam and is visible on almost every page in the application For example a requirements identifier is RQ Incidents are IN and tasks are TK The artifact ID is the number of the artifact So by creating a commit message that reads Due to requirement RQ 12 the code for toString in class XML parser was modified This also fixed Incident IN 1034 SpiraTeam will automatically detect the tokens and will include links to them under the Associations tab for each revision detail in SpiraTeam In addition when Jenkins creates the next build that includes this revision the plugin will automatically parse the revision message and convert the tokens into hyperlinks to the corresponding SpiraTeam artifact That way when developers view the build changelog in Jenkins it will automatically include links to the SpiraTeam items Jenkins Jenkins Build JUnit 97 Back to Project Build 97 Mar 14 2012 3 34 02 PM panah Revision 17861 Eal Changes 1 Fixed IN 7 and RQ 4 detail Previous Build o Started by anonymous user Meanwhile inside SpiraTeam the system will use the same information to automatically link the list of associated revisions to the build record Incidents Test Runs 17861 Fixed IN 7 and RQ 4 14 ez 2012 i Show s v m 4 4 Displaying page aa of 1 gt gt If the commit message contains Incident tokens the plugin will also automat
41. ssword Jabber Notifier Jabber account Version Control Username Settings You are not watching any build configurations Default for all of the VCS roots brgruber Spira Notifier For TeamCity You are watching all projects UI Settings Highlight my changes and investigations Windows Tray Notifier L Show date time in my timezone C Show all personal builds C Add builds triggered by me to favorites You are not watching any build configurations Once in the page click in Add new Rule Then inside the Send notification when section select the events you want TeamCity notify SpiraTeam General Groups Notification Rules Email Notifier 0 2 IDE Notifier 0 2 Jabber Notifier 0 1 Spira Notifier for TeamCity 0 Windows Tray Notifier 0 1 Add New Rule Watch Builds affected by my changes Edit Branch Filter Builds from the selected project Builds from the selected build configurations System wide events Send notification when M Build fails LJ Ignore failures not caused by my changes Only notify on the first failed build after successful M Build is successful LJ Only notify on the first successful build after failed The first build error occurs C Build starts Build fails to start Build is probably hanging Investigation is updated C Tests are muted or unmuted After selecting your preferences click in the Save button 3 4 Configuring a TeamCity Pro
42. st 125 Associations Revisions Incidents Test Runs This page will display the status success failure and details of the build imported from the Bamboo Console Output together with a list of the associated incidents test runs and source code revisions The following section will explain how to use your Source Code Management SCM system to take advantage of the SpiraTeam add on and automatically link incidents and source code revisions to the build information 4 5 Working with Source Code Changesets When your developers commit changes to your application s source into the SCM repository they should make sure to link the commit to the appropriate artifacts in SpiraTeam For example they may want to record that the revision fixes a specific incident or implements a specific feature requirement Linking an artifact is very simple All the developer needs to do is enter the artifact token in the following format PREFI X ID 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 tasks are TK The artifact ID is the number of the artifact So by creating a commit message that reads Due to requirement RQ 12 the code for toString in class XML parser was modified This also fixed Incident IN 1034 SpiraTeam will automatically detect t
43. the SpiraTeam Jenkins Plug in Now that the plugin has been installed you need to go back to the Jenkins homepage and click on the Manage Jenkins hyperlink followed by the Configure System hyperlink This will bring up the main Jenkins configuration page Scroll down to find the Spira Integeration section Spira Integration Spira URL http localhost SpiraTeam Username fredbloggs Password 999999999 Test Connection Enter in the URL you use to access your instance of SpiraTeam together with a valid username and password Once you have entered the values click on the Test Connection button to verify that Jenkins can connect to SpiraTeam successfully Once it has connected successfully click the Save button at the bottom of the screen to save your connection settings 2 4 Configuring a Jenkins Job Now that you have setup the global SpiraTeam settings in Jenkins next you need to associate each of your Jenkins Jobs with their corresponding SpiraTeam Project and Release Iteration To do this click on the name of the Jenkins Job and then click on the Configure hyperlink for that Job Project name Build JUnit BS Preview C Discard Old Builds This build is parameterized Disable Build No new builds will be executed until the project is re enabled Execute concurrent builds if necessary Advanced Project Options Source Code Management 8 0
44. ting svn doctor Common U test txt At revision 17861 14 Mar 2012 BL000042 F Build JUnit 93 14 Mar 2012 Failed 14 Mar 2012 BL000041 F Build JUnit 92 8 Mar 2012 Succeeded 0 8 Mar 2012 BL000040 F Build JUnit 89 8 Mar 2012 Succeeded 0 8 Mar 2012 BL000039 F Build JUnit 88 8 Mar 2012 Succeeded 0 8 Mar 2012 BL000038 If you have configured your Project Home to include the list of recent builds the build information will also be displayed on the Project Home dashboard Recent Builds Name Status Creation Date Build JUnit 97 s 3 14 2012 3 34 02 PM Build JUnit 96 5L ded 3 14 2012 3 33 15 PM JUnithworkspace Updating svn doctor Common At revision 1 660 no change for svn dactor Common since the previous build Clicking on either of the hyperlinks will allow you to navigate to the Build details page inside SpiraTeam Welcome System Administrator My Profile Administration Log Out e My Page Project Home Planning Testing Tracking Reporting amp spiraTeam ee Requirements Releases gt Build Details Iterations Planning Board lt lt Back To Build Lit Build Build JUnit 97 BL 000045 E N E Build JUnit 97 Build JUnit 97 b ti x A escription Started by user anonymous bula P 96 Building in workspace D Program Files Jenkins jobs Build JUnit workspace F Build JUnit 95 Updating svn doctor Common amp Build JUnit 94 ke m Build JUnit 93 t re
45. tion Spira Global Settings Project related Settings l Spira Configuration Projects i SpiraTeam URL hitp localhost Spira Build Time User Name spiralser Disk Usage Password ITTITIT Server Health Audit You will need TeamCity administrator privileges to access this configuration page Once in the Spira Global Settings page enter in the URL you use to access your instance of SpiraTeam together with a valid username and password Once you have entered the values click on the Save button TeamCity will then verify if it can connect to SpiraTeam successfully Once it has connected successfully your connection settings will be saved In case of error follow the instructions on screen and try again After setting the global configurations appropriately you will need to enable the notifications in TeamCity To do this go to My Settings amp Tools that can be accessed through clicking your TeamCity username top right Once there in the General tab inside the Watched Builds and Notifications box find the Spira Notifier for TeamCity section and click in Edit T Projects Changes Agents 1 amp Build Queue 0 My Settings amp Tools General Groups Notification Rules General Watched Builds and Notifications Email Notifier Username You are not watching any build configurations Name Email address IDE Notifier Password You are not watching any build configurations Confirm pa
46. vision 1 66 ica Build JUnit 92 Status Succeeded Creation Date 3 14 2012 3 34 02 PM 8 Build JUnit 89 Last Updated 3 14 2012 3 34 04 PM Build JUnit 88 Build JUnit 87 Revisions Test Runs ap enn V 6 IncidentName AY TypeAY StatusAY Priority V Detected By AV po lt 8 Build JUnit 82 E o E Cannot add a new book to the system Bug Assigned 1 Critical Joe P Smith 4 Nov 200 Build JUnit 81 Show 15 v rows per page ma D a This page will display the status success failure and details of the build from the Jenkins Console Output together with a list of the associated incidents test runs and source code revisions The following section will explain how to use your Source Code Management SCM system to take advantage of the SpiraTeam plugin and automatically link incidents and source code revisions to the build information 2 6 Working with Source Code Changesets When your developers commit changes to your application s source into the SCM repository they should make sure to link the commit to the appropriate artifacts in SpiraTeam For example they may want to record that the revision fixes a specific incident or implements a specific feature requirement Linking an artifact is very simple All the developer needs to do is enter the artifact token in the following format PREFI X ID The first half the Artifact Identifier is a two letter code that is used th
47. your SpiraTeam user name here lt add name SpiraPassw value Enter your SpiraTeam password here lt add name SpiraPnumber value Enter your SpiraTeam project here add name SpiraPvers value Enter your SpiraTeam release version here The information you need to enter is e SpiraURL It is the URL you use to access your instance of SpiraTeam e SpiraUser Your Spiraleam user name e SpiraPassw Your SpiraTeam password e SpiraPnumber The numeric ID of the SpiraTeam Project that the Build belongs to e g for Project PR00001 just enter 1 e SpiraPvers The version number of the SpiraTeam Release Iteration that the Build belongs to e g for Release RL0004 with version number 1 0 0 0 you d enter just 1 0 0 0 Additionally you can specify the TFS project you want to associate with the SpiraProject you have setup entering the TFS Project name in the appropriate field inside the eventRules section teamProject Enter your TFS project name here Make sure to enter the exactly project name you have in TFS If you leave this field blank the associated SpiraTeam project will receive notifications from all the projects in TFS Here is an example of how your configuration file should look like after the setup bots bot id spira type DevCore TfsNotificationRelay SpiraTeam SpiraNotifier DevCore TfsNotificationRelay SpiraTeam textId slacktext lt botSettings gt 1 Please enter t
Download Pdf Manuals
Related Search