Starteam Best Practices

Total Page:16

File Type:pdf, Size:1020Kb

Starteam Best Practices . StarTeam Best Practices ........ A guide to StarTeam’s general architecture and how to use StarTeam with your software development processes Table of Contents CONTENTS .................................................................................................................................................................2 INTRODUCTION .......................................................................................................................................................4 STARTEAM OVERVIEW.........................................................................................................................................4 THE STARTEAM MODEL .......................................................................................................................................5 THE STARTEAM REPOSITORY.....................................................................................................................................5 CLIENT SERVER ARCHITECTURE ................................................................................................................................5 PROJECT-ORIENTATION..............................................................................................................................................6 ITEMS .........................................................................................................................................................................7 PROJECTS ...................................................................................................................................................................8 VIEWS ........................................................................................................................................................................8 FOLDERS ....................................................................................................................................................................9 VIEW LABELS...........................................................................................................................................................10 BRANCHING VIEWS ..................................................................................................................................................10 MERGING VIEWS ......................................................................................................................................................12 LINKING ...................................................................................................................................................................12 FILE STATUS.............................................................................................................................................................13 USE CASES ...............................................................................................................................................................14 I. RELEASE DEVELOPMENT AND MAIN DEVELOPMENT............................................................................................14 Sample Scenario 1 ...............................................................................................................................................14 Using a New View to Resolve Scenario 1............................................................................................................14 Using Labels to Resolve Scenario 1 ....................................................................................................................14 Sample Scenario 2 ...............................................................................................................................................17 Using Promotion States to Resolve Scenario 2....................................................................................................17 II. BUG FIXES ...........................................................................................................................................................19 Using a Fix or Maintenance Branch to Resolve Scenario 3................................................................................20 III. INDEPENDENT PRODUCT DEVELOPMENT............................................................................................................20 Sample Scenario 4 ...............................................................................................................................................20 Using a New Branch to Resolve Scenario 4 ........................................................................................................21 IV. COMMON COMPONENT LIBRARY DEVELOPMENT ..............................................................................................21 Setting up the Build Process................................................................................................................................22 Checking Out by Build Label...............................................................................................................................22 Checking Out by Promotion State .......................................................................................................................22 V. CONFIGURATION IDENTIFICATION REPORTS........................................................................................................23 Creating a Filter..................................................................................................................................................23 Displaying Modified Files and Generating the Report........................................................................................26 VI. STAGING ............................................................................................................................................................28 Phase 1: Creating Promotion States for Your Stages..........................................................................................28 Phase 2: Creating a View for the Test Stage ..................................................................................................29 Phase 3: Creating a View for the Production Stage.......................................................................................30 TIPS FOR STARTEAM 4.1 .....................................................................................................................................30 Databases ............................................................................................................................................................31 Project Structure..................................................................................................................................................31 Folders.................................................................................................................................................................31 Backups................................................................................................................................................................31 SECURITY .................................................................................................................................................................32 From StarTeam VirtualTeam Server ...................................................................................................................33 From StarTeam....................................................................................................................................................33 MANIPULATING FOLDERS AND ITEMS IN STARTEAM ...............................................................................................34 2 LABELS ....................................................................................................................................................................35 View Labels .........................................................................................................................................................36 Revision Labels....................................................................................................................................................37 PROMOTION STATES.................................................................................................................................................37 CHANGE REQUESTS..................................................................................................................................................38 TOPICS......................................................................................................................................................................38 TASKS ......................................................................................................................................................................39 GLOSSARY ...............................................................................................................................................................40 3 Introduction StarTeam has revolutionized software configuration management (SCM) applications by saving your company time, money, and code integrity. Since StarTeam’s inception, we have learned from our own experiences and that of our customers about the best ways to install, configure and use StarTeam. We’d like to share this knowledge and information with you. This document includes: ÿ StarTeam Overview A general description
Recommended publications
  • Pragmatic Version Control Using Subversion
    What readers are saying about Pragmatic Version Control using Subversion I expected a lot, but you surprised me with even more. Hav- ing used CVS for years I hesitated to try Subversion until now, although I knew it would solve many of the shortcom- ings of CVS. After reading your book, my excuses to stay with CVS disappeared. Oh, and coming from the Pragmatic Bookshelf this book is fun to read too. Thanks Mike. Steffen Gemkow Managing Director, ObjectFab GmbH I’m a long-time user of CVS and I’ve been skeptical of Sub- version, wondering if it would ever be “ready for prime time.” Until now. Thanks to Mike Mason for writing a clear, con- cise, gentle introduction to this new tool. After reading this book, I’m actually excited about the possibilities for version control that Subversion brings to the table. David Rupp Senior Software Engineer, Great-West Life & Annuity This was exactly the Subversion book I was waiting for. As a long-time Perforce and CVS user and administrator, and in my role as an agile tools coach, I wanted a compact book that told me just what I needed to know. This is it. Within a couple of hours I was up and running against remote Subversion servers, and setting up my own local servers too. Mike uses a lot of command-line examples to guide the reader, and as a Windows user I was worried at first. My fears were unfounded though—Mike’s examples were so clear that I think I’ll stick to using the command line from now on! I thoroughly recommend this book to anyone getting started using or administering Subversion.
    [Show full text]
  • Version Control 101 Exported from Please Visit the Link for the Latest Version and the Best Typesetting
    Version Control 101 Exported from http://cepsltb4.curent.utk.edu/wiki/efficiency/vcs, please visit the link for the latest version and the best typesetting. Version Control 101 is created in the hope to minimize the regret from lost files or untracked changes. There are two things I regret. I should have learned Python instead of MATLAB, and I should have learned version control earlier. Version control is like a time machine. It allows you to go back in time and find out history files. You might have heard of GitHub and Git and probably how steep the learning curve is. Version control is not just Git. Dropbox can do version control as well, for a limited time. This tutorial will get you started with some version control concepts from Dropbox to Git for your needs. More importantly, some general rules are suggested to minimize the chance of file losses. Contents Version Control 101 .............................................................................................................................. 1 General Rules ................................................................................................................................... 2 Version Control for Files ................................................................................................................... 2 DropBox or Google Drive ............................................................................................................. 2 Version Control on Confluence ...................................................................................................
    [Show full text]
  • Microservices and Monorepos
    Microservices and Monorepos Match made in heaven? Sven Erik Knop, Perforce Software Overview . Microservices refresher . Microservices and versioning . What are Monorepos and why use them? . These two concepts seem to contradict – why mix them together? . The magic of narrow cloning . A match made in heaven! 2 Why Microservices? . Monolithic approach: App 3 Database Microservices approach . Individual Services 4 DB DB Database Versioning Microservices . Code . Executables and Containers . Configuration . Natural choice: individual repositories for each service Git . But: • Security • Visibility • Refactoring • Single change id to rule them all? 5 Monorepo . Why would you use a monorepo? . Who is using monorepos? . How would you use a monorepo? 6 Monorepos: Why would you do this? . Single Source of Truth for all projects . Simplified security . Configuration and Refactoring across entire application . Single change id across all projects . Examples: • Google, Facebook, Twitter, Salesforce, ... 7 Single change across projects change 314156 8 Monorepos: Antipatterns User workspace User workspace 9 Monorepos – view mapping User workspace . Map one or more services . Users only access files they need . Simplified pushing of changes 10 What does this have to do with Git? . Git does not support Monorepos • Limitations on number and size of files, history, contributing users • Companies have tried and failed . Android source spread over a thousand Git repositories • Requires repo and gerrit to work with 11 How can we square this circle? https://en.wikipedia.org/wiki/Squaring_the_circle 12 Narrow cloning! . Clone individual projects/services . Clone a group of projects into a single repo 13 Working with narrowly cloned repos . Users work normally in Git . Fetch and push changes from and to monorepo .
    [Show full text]
  • Code Review Is an Architectural Necessity
    Code review is an architectural necessity Colin Dean @colindean 1 @ColinDean Software Engineer Organizer, Abstractions.io Wearer of many hats 2 My words are my own and not my employer(s), past or present. Please save questions until the end of the presentation. 3 Agenda • Quick anecdote • What is code review? • What problems does code review solve? • Quality attributes code review ensures • Tips for code reviews • Limitations 4 5 Agenda • Quick anecdote • What is code review? • What problems do code review solve? • Quality attributes code review ensures • Tips for code reviews • Limitations 6 What is code review? 7 Code review is the process by which those who maintain a software codebase evaluate a proposed change to that codebase, regardless of the source of the proposed change. 8 Code review is systematic examination of computer source code. Code Review, Wikipedia 9 Peer Review 10 Code Review 11 Code Review Vocabulary • Change - an individual unit of work altering what exists • Submission - a collection of changes • Submitter - the person proposing the submission • Reviewer - the people evaluating the submission • Annotation - remarks or ratings bestowed upon the submission 12 The submitter proposes changes in a submission, which is evaluated by a reviewer, who annotates or accepts it. 13 Most formal Least formal Team Pair Peer Inspection Walkthrough Ad-hoc review review programming deskcheck, passaround Wiegers’ peer review formality spectrum 14 Most formal Least formal Team Pair Peer Inspection Walkthrough Ad-hoc review review programming deskcheck, passaround Wiegers’ peer review formality spectrum 15 16 Agenda • Quick anecdote • What is code review? • What problems does code review solve? • Quality attributes code review ensures • Tips for code reviews • Limitations 17 Aside from the primary goal of reducing defects, Code review solves two major problems.
    [Show full text]
  • Version Control – Agile Workflow with Git/Github
    Version Control – Agile Workflow with Git/GitHub 19/20 November 2019 | Guido Trensch (JSC, SimLab Neuroscience) Content Motivation Version Control Systems (VCS) Understanding Git GitHub (Agile Workflow) References Forschungszentrum Jülich, JSC:SimLab Neuroscience 2 Content Motivation Version Control Systems (VCS) Understanding Git GitHub (Agile Workflow) References Forschungszentrum Jülich, JSC:SimLab Neuroscience 3 Motivation • Version control is one aspect of configuration management (CM). The main CM processes are concerned with: • System building • Preparing software for releases and keeping track of system versions. • Change management • Keeping track of requests for changes, working out the costs and impact. • Release management • Preparing software for releases and keeping track of system versions. • Version control • Keep track of different versions of software components and allow independent development. [Ian Sommerville,“Software Engineering”] Forschungszentrum Jülich, JSC:SimLab Neuroscience 4 Motivation • Keep track of different versions of software components • Identify, store, organize and control revisions and access to it • Essential for the organization of multi-developer projects is independent development • Ensure that changes made by different developers do not interfere with each other • Provide strategies to solve conflicts CONFLICT Alice Bob Forschungszentrum Jülich, JSC:SimLab Neuroscience 5 Content Motivation Version Control Systems (VCS) Understanding Git GitHub (Agile Workflow) References Forschungszentrum Jülich,
    [Show full text]
  • Visual Build Help
    Visual Build Professional User's Manual Copyright © 1999-2021 Kinook Software, Inc. Contents I Table of Contents Part I Introduction 1 1 Overview ................................................................................................................................... 1 2 Why Visual................................................................................................................................... Build? 1 3 New Features................................................................................................................................... 2 Version 4 .......................................................................................................................................................... 2 Version 5 .......................................................................................................................................................... 3 Version 6 .......................................................................................................................................................... 4 Version 7 .......................................................................................................................................................... 7 Version 8 .......................................................................................................................................................... 9 Version 9 .........................................................................................................................................................
    [Show full text]
  • Distributed Revision Control with Mercurial
    Distributed revision control with Mercurial Bryan O’Sullivan Copyright c 2006, 2007 Bryan O’Sullivan. This material may be distributed only subject to the terms and conditions set forth in version 1.0 of the Open Publication License. Please refer to Appendix D for the license text. This book was prepared from rev 028543f67bea, dated 2008-08-20 15:27 -0700, using rev a58a611c320f of Mercurial. Contents Contents i Preface 2 0.1 This book is a work in progress ...................................... 2 0.2 About the examples in this book ..................................... 2 0.3 Colophon—this book is Free ....................................... 2 1 Introduction 3 1.1 About revision control .......................................... 3 1.1.1 Why use revision control? .................................... 3 1.1.2 The many names of revision control ............................... 4 1.2 A short history of revision control .................................... 4 1.3 Trends in revision control ......................................... 5 1.4 A few of the advantages of distributed revision control ......................... 5 1.4.1 Advantages for open source projects ............................... 6 1.4.2 Advantages for commercial projects ............................... 6 1.5 Why choose Mercurial? .......................................... 7 1.6 Mercurial compared with other tools ................................... 7 1.6.1 Subversion ............................................ 7 1.6.2 Git ................................................ 8 1.6.3
    [Show full text]
  • Scaling Git with Bitbucket Data Center
    Scaling Git with Bitbucket Data Center Considerations for large teams switching to Git Contents What is Git, why do I want it, and why is it hard to scale? 01 Scaling Git with Bitbucket Data Center 05 What about compliance? 11 Why choose Bitbucket Data Center? 13 01 What is Git, why do I want it, and why is it hard to scale? So. Your software team is expanding and taking on more high-value projects. That’s great news! The bad news, however, is that your centralized version control system isn’t really cutting it anymore. For growing IT organizations, Some of the key benefits Codebase safety moving to a distributed version control system is now of adopting Git are: Git is designed with maintaining the integrity considered an inevitable shift. This paper outlines some of managed source code as a top priority, using secure algorithms to preserve your code, change of the benefits of Git as a distributed version control system history, and traceability against both accidental and how Bitbucket Data Center can help your company scale and malicious change. Distributed development its Git-powered operations smoothly. Community Distributed development gives each developer a working copy of the full repository history, Git has become the expected version control making development faster by speeding up systems in many circles, and is very popular As software development increases in complexity, and the commit process and reducing developers’ among open source projects. This means its easy development teams become more globalized, centralized interdependence, as well as their dependence to take advantage of third party libraries and on a network connection.
    [Show full text]
  • Versie Beheer Systemen (VCS) 1
    Versie beheer systemen (VCS) 1 Computerclub Volwassenen, Jeugd en Informatica vzw www.vji.be Versie beheer systemen (VCS) Inleiding ..................................................................................................................................... 2 Beheer repository en client programma’s .............................................................................. 2 In- en uitchecken, merging, labeling, branching.................................................................... 2 Software ..................................................................................................................................... 3 Microsoft Visual SourceSafe (VSS) ...................................................................................... 3 SourceOffSite..................................................................................................................... 3 VSSConnexion................................................................................................................... 3 Borland StarTeam .................................................................................................................. 3 CVS (Concurrent Versions System) ...................................................................................... 4 CvsGui................................................................................................................................4 TortoiseCVS......................................................................................................................
    [Show full text]
  • Starteam 16.2
    StarTeam 16.2 Release Notes Micro Focus The Lawn 22-30 Old Bath Road Newbury, Berkshire RG14 1QN UK http://www.microfocus.com Copyright © Micro Focus 2017. All rights reserved. MICRO FOCUS, the Micro Focus logo and StarTeam are trademarks or registered trademarks of Micro Focus IP Development Limited or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries. All other marks are the property of their respective owners. 2017-11-02 ii Contents StarTeam Release Notes ....................................................................................5 What's New ........................................................................................................ 6 16.2 ..................................................................................................................................... 6 StarTeam Command Line Tools .............................................................................. 6 StarTeam Cross-Platform Client ...............................................................................6 StarTeam Git Command Line Utility. .........................................................................7 StarTeam Server ...................................................................................................... 7 Workflow Extensions ................................................................................................ 8 StarTeam Web Client ................................................................................................8 16.1 Update 1 ......................................................................................................................9
    [Show full text]
  • Teamcity 7.1 Documentation.Pdf
    1. TeamCity Documentation . 4 1.1 What's New in TeamCity 7.1 . 5 1.2 What's New in TeamCity 7.0 . 14 1.3 Getting Started . 26 1.4 Concepts . 30 1.4.1 Agent Home Directory . 31 1.4.2 Agent Requirements . 32 1.4.3 Agent Work Directory . 32 1.4.4 Authentication Scheme . 33 1.4.5 Build Agent . 33 1.4.6 Build Artifact . 34 1.4.7 Build Chain . 35 1.4.8 Build Checkout Directory . 36 1.4.9 Build Configuration . 37 1.4.10 Build Configuration Template . 38 1.4.11 Build Grid . 39 1.4.12 Build History . 40 1.4.13 Build Log . 40 1.4.14 Build Number . 40 1.4.15 Build Queue . 40 1.4.16 Build Runner . 41 1.4.17 Build State . 41 1.4.18 Build Tag . 42 1.4.19 Build Working Directory . 43 1.4.20 Change . 43 1.4.21 Change State . 43 1.4.22 Clean Checkout . 44 1.4.23 Clean-Up . 45 1.4.24 Code Coverage . 46 1.4.25 Code Duplicates . 47 1.4.26 Code Inspection . 47 1.4.27 Continuous Integration . 47 1.4.28 Dependent Build . 47 1.4.29 Difference Viewer . 49 1.4.30 Guest User . 50 1.4.31 History Build . 51 1.4.32 Notifier . 51 1.4.33 Personal Build . 52 1.4.34 Pinned Build . 52 1.4.35 Pre-Tested (Delayed) Commit . 52 1.4.36 Project . 53 1.4.37 Remote Run . ..
    [Show full text]
  • Tasktop Integration Hub Editions.Pdf
    TASKTOP EDITIONS Tasktop provides organizations the capabilities needed to transform software delivery by integrating their entire value stream. Choose which edition is right for your business. PRO ENTERPRISE ULTIMATE Starter package For organizations For organizations for integrating two interested in that want the benefit Lifecycle tools. connecting part of of a fully integrated their software delivery software delivery value stream. value stream. From $12.50 Request a Quote Request a Quote Endpoint Connector Types per user, per month* Connect Any 2 Connect up to 5 Lifecycle Tools Unlimited Lifecycle Tools Lifecycle Tools DevOps Tools - $ Unlimited Database Tools - $ Unlimited Enterprise Integration Support PRO ENTERPRISE ULTIMATE Integration Designer Web-based integration designer and administra- tion interface for configuring integrations Rapid Project Scaling Scale to hundreds of projects with just a few clicks Attachment Synchronization Share screenshots and diagrams along with your artifacts Comment Synchronization Use comments for in-context collaboration Smart Mappings Automatically maps common artifact attributes Smart Change Detection Optimized for high-performance Model-based Integration Management Included and Custom Included and Custom Map artifacts to a central model instead of Included Models Models Models creating endless tool pairs Artifact Relationship Management Maintain critical context by mirroring 1 Relationship Unlimited Relationships Unlimited Relationships relationships like parent-child, validated by or blocked
    [Show full text]