Manuals / IBM / Computer Equipment / Personal Computer

IBM SC34-4499-03 manual Closing a defect, Integrate Work Areas window

Models: SC34-4499-03

1 356

Download 356 pages 55.74 Kb

Page 89

Figure 19. Integrate Work Areas window

Command

From a command line, he issues the following command:

teamc workarea -integrate 310 -release robot_control

Result

TeamConnection ®rst determines that Alex's changes were built against the latest version of the release. Then TeamConnection makes Alex's changes visible at the release level so that the other team members can see and use them. The following part versions are now visible from the release:

brain.c (Jenny©s modification) brain.obj (from Jenny©s build) brain.exe (from Alex©s build) arm.c

arm.obj

hand.c (Joy©s modification, Ken©s modification) hand.obj (from Ken©s build)

leg.c

leg.obj

foot.c

foot.obj

optics.c (Alex©s modification 5) optics.obj (from Alex©s build)

TeamConnection also makes a copy of the release before integrating Alex's changes. If something doesn't work, the users or the administrator can go back to the release prior to Alex's integration. The part, optics.c, is now unlocked in the release. The work area is now in the complete state and can no longer be used.

Closing a defect

Now that Alex is ®nished making changes to ®x the problem reported in defect 310, he is ready to close the defect. He does one of the following:

GUI

Chapter 5. Working with no component or release processes 69

Image 89

IBM SC34-4499-03 manual Closing a defect, Integrate Work Areas window

Contents

IBM Page IBM Fourth Edition March Contents Working with component and release processes States of TeamConnection objectsWorking with no component or release processes Part 4. Using TeamConnection to build applications Part 3. Using TeamConnection Notes Integrated DatabasesIntroduction to TeamConnection Integrated Notes Databases Creating and Maintaining Integrated Notes DatabasesWorking with build scripts and builders Installing, starting, and stopping build serversWorking with MVS build scripts and builders Working with parsers Creating a parserPart 5. Using TeamConnection to package products Appendix J. Sample Rexx execs, build scripts, and parsers Appendix G. Source Code Control Users GuideAppendix H. Supported expandable keywords Readers Comments Ð Wed Like to Hear from You Users Guide Figures Xii Users Guide Xiii Xiv Users Guide Trademarks Xvi Users Guide How this book is organized About this bookConventions XviiTell us what you think Part 1. Introducing TeamConnection Users Guide An introduction to TeamConnection TeamConnections client/server architecture TeamConnection denitionsInterfaces TeamConnection databaseParts FamiliesUsers and host lists Check ComponentsCheck out Work areas ReleasesDrivers Processes Defects and featuresApproval BuildFamily administrator System administratorPackaging Roles people playEnd user Build administratorUsers Guide Part 2. Developing a product using TeamConnection Working with component and release processes Getting familiar with the TeamConnection client interfaces Using the GUITasks window Starting the GUIPerforming tasks with the GUI Stopping the GUIOn the GUI Using the Settings notebookOnline help information Using the command line interfaceUsing the TeamConnection web client Getting familiar with the TeamConnection client interfaces Users Guide Laying the groundwork Basics of using TeamConnectionComponents window Authority to perform tasksFinding parts Finding objects within TeamConnectionPartFull Using work areasBuildView Creating parts Naming your work areasPreparing to build your parts Naming your partsDependent Working in serial or concurrent development modeWorking with parts Working with common parts Your workstations current working directory Getting parts from TeamConnectionChecking parts in to TeamConnection Versioning releases Finding different versions of TeamConnection objectsVersioning work areas Versioning drivers Analyzing defects and features Working with defects and featuresDesigning the resolution Versioning partsResolving defects and implementing features Testing and verifying part changesVerifying the resolution of the defect or feature Reviewing the design and resource estimatesUsers Guide Component subprocesses States of TeamConnection objectsRelease subprocesses Open stateReturned state Canceled stateDesign state Size stateVerify state Review stateWorking state Closed state Fix state States of work areasApprove state Integrate state Restrict state States of driversCommit state Test stateRestrict state Verication and test records Users Guide Working in serial development Working with no component or release processesFor information about this task Go to this Accepting a defectResult CommandCreating a work area Create Work Areas window Checking out a partCheck Out Parts window Searching for a partPart Filter window Selects Save to Task ListEdit Task List window Checking in a part Teamc part -checkin optics.c -release robotcontrol -workarea Thus, work area 310 contains the following parts Verifying and testing part updatesBuild Parts window Extract Parts window Extracting a partCheck Out Parts Checking out the part one more timeChecking the part back Now the work area contains the following parts Freezing the work areaRefreshing the work area Refresh Work Areas window Building the applicationIntegrating the work area Integrate Work Areas window Closing a defectVerify Defects window Working in concurrent developmentFollowing tasks are required Refreshing the work area from the driverFrom a command line, she issues the following command Reconciling differences GUI Reconcile Collision Record window Result Working with component and release processes Moving through design, size, and review Results Changing defect ownershipAccepting a defect Approving Accept Approval Records window \robot\src in the Destination directory eld\robot\src in the Source directory eld Checking in the changesNow the work area contains the following part versions Teamc workarea -freeze 456 -release robotcontrol Building the application Complete Fix Records window Accepting x recordsAdding a driver member Integrating changed parts into a releaseReturning the work area to the x state Reconciling the differencesActivate Fix Records window Reactivating the x recordRefreshing the driver Refresh Drivers window Building the driverRestricting the driver Restrict Drivers window Integrating the partsComplete Drivers window Completing the driverAccept Test Records window Testing the built applicationRetrieving a past version of a part Using a congured processTeamc workarea -freeze 1208 -release robotcontrol Working with component and release processes TeamConnection system returns the following report 101 Part 3. Using TeamConnection Notes Integrated DatabasesUsers Guide 103 Introduction to TeamConnection Integrated Notes DatabasesGetting started Sources of user information Using TeamConnection with Lotus NotesPrerequisites and dependencies Database types Test Case Management and Tracking Forms and subformsGeneric User DenedRequirements ViewsAll documents Document archiving ReviewsUsers Guide 111 Important notice to administratorsCreating and Maintaining Integrated Notes Databases Initializing the original template and creating a database Select Access Control Users Guide Select File-Save Select Administration-Document ControlCreating customized production databases Select Administration-Document Control Performing reconciliation From the File menu, select Database-Replace Design Database maintenance refreshing design from a templateImportant notice to administrators 121 Rules of thumb and general adviceDatabase Design Strategies and Advanced Customization Using the Customization setup facility Common Database Options Modify Database Optional InformationDatabase-specic Options Modify the document hierarchyReconciliation of Notes and TeamConnection Data Modify TeamConnection AccessLog Document Options Activate Reconcile Defects and FeaturesAdvanced customization Users Guide 127 Part 4. Using TeamConnection to build applicationsBasic build concepts Working with parsersBuilding an application an example 129 Basic build conceptsPhysical structure of the build function TeamConnection part Build object modelBuild event BuilderBuild script Parent-child relationships in a build treeInput parts Output partsUsers Guide Sample build object model for msgcat.exe Working with a build treeBuild tree for the hello application For more information about this task Go to this Putting the pieces togetherFor more information about this task Go to this Installing the build function Installing, starting, and stopping build serversCreating a build server on MVS 137Cd JCL data set for load module Cd data set for teamproc jcl Creating a build server on MVS/OEStarting build servers using teamcbld Starting an MVS build server Runpgm Exec PGM=TEAMCBLD Starting the MVS/OE build server Creating build startup les for non-MVS environments Stopping an MVS build server Stopping the build serversUsers Guide 147 Working with build scripts and buildersCreating a builder Release Fromscriptfilespec -scriptnameEnvironment Writing a build script TimeoutComparison operator and RC value ParametersAs attributes of a builder Passing parameters to a build scriptAs attributes of a part in the build tree As parameters of the part -build commandWriting an executable le for a build script Writing a simple build scriptTesting a build script Putting a builder to work Modifying the contents of a build scriptModify Part Properties window Removing a builder from a partWorking with VisualAge C++ and Templates Users Guide 159 Working with MVS build scripts and buildersCreating a builder for MVS builds Builder File type none Script null Script, File type, and Source leFile type none Script fhbc Comparison operator are as follows ± EQ or == Equals Fhbmasm.jcl Writing an MVS build scriptFhbcobm.jcl Fhbmpli.jclPassing parameters to an MVS build script File name conversions for MVSTcbldusr TeamConnection syntax for MVS build scriptsExec statement Supported JCL syntaxPositional parameters Keyword parametersDD Statement Example of a build script for a C compile WELLSK.TEAMC.ERRORWorking with MVS build scripts and builders UNIT=SYSDA,SPACE=TRK,10,5 Example of a build script for a Cobol compileDCB=RECFM=FB,LRECL=80,BLKSIZE=3200 Example of a build script for a linkSysmod DD TCEXT=LOAD,DISP=NEW,DELETE Working with MVS build scripts and builders Users Guide 175 Working with parsersCreating a parser Create Parser window IncludeWriting a parser command le Putting a parser to work Removing a parser from a part From a command line, type the following 181 Building an application an exampleSample build tree Starting the build servers Mvspool Creating builders and parsersCreating the build tree for the application Create Parts window Create Parts window Modify Part Properties window Connect Parts window Build tree display Starting the build on the clientBuild target Build modeWork area Build poolDetail le name Putting the build scripts to workUnconditional Monitoring the progress of a build Finishing the job and reporting the results to the userBuilding all parts, regardless of build times Running a build in spite of errorsFinding out which parts will be built Canceling a buildDening multiple outputs from a single build event More sample build treesHe creates the collector part Synchronizing the build of unrelated partsBuilding an application an example Users Guide Chapter Using TeamConnection to package a product Part 5. Using TeamConnection to package products199 ChapterUsers Guide 201 Using TeamConnection to package a productSetting up a build tree for the gather tool Setting up your build tree for packagingShe also connects a readme le for the application Adding the gather step to the build tree 205 Using the Gather toolUsing the teamcpak command for the Gather tool Inputles Command line ¯agsString Using the Gather tool Syntax rules for a Gather package le Examples of the teamcpak gather commandWriting a package le for the Gather tool Targetroot targetrootpath Keywords for a Gather package lePackageformat gather Source list of le specications Target Targetpath EXITPRIOR, EXITPOST, and Exitreplace String Using exit keywords in the Data clauseUsing exit keywords in the Rule clause Package le looks like this Using exit keywords an exampleUsers Guide 215 Using the Tivoli Software Distribution packaging toolInputFile Syntax rules for a Tivoli Software Distribution package le Example of the teamcpak softdist commandWriting a package le for Tivoli Software Distribution Packageformat softdist Keywords for a Tivoli Software Distribution package leExample Nodes Installpgm Log le Sample package leOption Trace facilityProfile Using the Tivoli Software Distribution packaging tool Exit # end of file 225 Part 6. AppendixesUsers Guide 227 Appendix A. Environment VariablesNlspath Tcbuildpool Tccasesense Tcmakeimportverbose Tcrelease TeamConnection dynamically set build environment variables Setting environment variables 235 Appendix B. Importing makele information into TeamConnectionConnect le Modied makeleCreate le Creating a rules le ContentLe mask ConnectComponent 239 Appendix C. TeamConnection MergeParameter Description 241 Creating a TeamConnection-enabled Workframe projectSetting up your project options Project actions Using your TeamConnection Workframe projectView part information Part actionsEdit part Show partsUsing your project a simple scenario Tcuser 245Tcbecome TC Extract Part TC View Part ContentsTC View Part Information TC Build PartUsers Guide 249 Overview of the ENVY/Manager-TeamConnection BridgeScope of this documentation Preparing to use the ENVY/Manager-TeamConnection Bridge How the bridge communicates with TeamConnectionEnvironment variables Setting up the bridge environmentPrerequisites Loading the ENVY/Manager-TeamConnection Bridge Testing the ENVY/Manager-TeamConnection Bridge Defaults Using the ENVY/Manager-TeamConnection BridgeSetting default properties Locking ContextOperations Import Exporting Envy components to TeamConnection ExportReplace existing les Storage in TeamConnectionExporting conguration maps and applications Importing Envy components from TeamConnection Exporting lesScenario assumptions VisualAge Generator Developer TeamConnectionEnvy Build generation Object mapping in TeamConnectionTeamConnection build function TeamConnection change control Making a change to a memberTeamConnection change control 267 Appendix G. Source Code Control Users GuideProjects vs Families Installing the TeamConnection source code control DLL Using TeamConnection as your source code control provider Connecting TeamConnection to an IDERemoving the TeamConnection Source Code Control DLL Before you startOpening a project Integrated featuresCheck-in Full features of TeamConnectionCheck-out Uncheck-outMigrating project data bases Starting a new project Users Guide 275 Appendix H. Supported expandable keywordsThen the expanded keywords will look like 277 Associated release ApprovalReject Approval record owner Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page New test record owner, subscribers Page Page Page Users Guide 301 Appendix J. Sample Rexx execs, build scripts, and parsersSample Rexx execs Script name Function Inputs DrvrMem Lists the defect and feature members of a DriverName Script name Function Inputs Sample build scripts Sample package les Sample parsers307 Customer supportIBM Talklink InternetDB2 service maintenance and technical library 309 BibliographyIBM VisualAge TeamConnection Enterprise Server library TeamConnection technical reports Glossary Related publicationsUsers Guide 313 GlossaryCompare to Contrast withUsers Guide Glossary End user. See user See also build dependentHPFS. See high-performance le system Users Guide Pool. See build pool Users Guide TeamConnection superuser. See superuser Users Guide 323 IndexBuilder Debug GUI Exitpost Parts nding Releases Tcmakeimportrules 227, 235 Work area Automatic creation Users Guide How satised are you that the information in this book is Readers Comments Ð Wed Like to Hear from YouReaders Comments Ð Wed Like to Hear from You IbmrPage Ibmr