Post on 07-Apr-2018
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 1/21
February 10, 2005
ClearCase/UCM FundamentalsWindows
Basic ClearCase
Usage
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 2/21
2
ClearCase/UCM Fundamentals
Course Objectives
By the end of this course, you will understand:
The nature of the ClearCase file system
Basic file versioning operations UCM objects and concepts
Development workflow through UCM
Working in a project and delivering your changes
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 3/21
3
ClearCase/UCM Fundamentals
Dynamic File System
Multi-Version File
System (MVFS)
Transparentaccess to
versions from
standard
development tools Handles low-level
file input/output
operations
open() dir
type
nonnon--versionedversioned
filesfiles
nonnon--versionedversioned
filesfiles
versioned filesversioned files
versioned filesversioned files
ClearCase MVFSClearCase MVFS
ClearCase MVFSClearCase MVFS
close()
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 4/21
4
ClearCase/UCM Fundamentals
The View is Your Workspace
Virtual workspace for an individual user
Selects versions of files and directories to work
with Allows developers to work without interfering
with each other
Each user may have multiple views
views for new development
views for integration activities
views for different development projects
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 5/21
5
ClearCase/UCM Fundamentals
Versions are Stored in Elements
An element is comprised
of a set of versions,
organized into a version
tree Any file which can be
stored on the Windows
file system can be
versioned in ClearCaseas an element:
text files
binary files
directoriesVersions
Labels
Branches
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 6/21
6
ClearCase/UCM Fundamentals
Versions, Branches and Labels
Versions are organizedin branches in eachelement
Only one version of anelement can be seen ina view directory
Labels are applied toone version in many
elements to create aproject wide baseline
Merge lines betweenbranches are also saved Versions
Labels
Branches
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 7/21
7
ClearCase/UCM Fundamentals
Elements are Stored in VOBs
Versioned Object Base (VOB) is a repository of
ClearCase elements
Element versions, branches, labels, and other database information is stored in a VOB
VOB name located at top level of view
directory structure
A network-wide file system resource
A project may work on more than one VOB
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 8/21
8
ClearCase/UCM Fundamentals
VOB
foo.cbar.c
View
Version Selection in a View
A view selectively filters a version of each
element
The view¶s configuration determines whichversion to select
bin src
foo.c
bar.c
project
configuration
V
I
E
W
server
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 9/21
9
ClearCase/UCM Fundamentals
View
View-Private Files
Files that are not under version control are
called view-private files. They are located
locally in the view storage
A view¶s directory can consist of both VOB
elements and view-private files VOB
foo.cbar.c
test.txt
View Storage
bin src
foo.c
bar.c
project
V
I
E
W
test.txt
your computer
server
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 10/21
10
ClearCase/UCM Fundamentals
VOB
foo.cbar.c
foo.c
View Storage
your computer
Checked Out Versions
Checked out element versions are copied to the view
storage
Any engineer can see your checked out version in the
version tree tool
bin src
foo.c
bar.c
project
View
V
I
E
W
server
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 11/21
11
ClearCase/UCM Fundamentals
UCM Overview
Activity based development process
grouping a set of changes in a single object
A set of tools and objects a level aboveversions, branches, labels and views
Each UCM object manages a lower level ClearCase
basic type with additional process features
Workflow for making changes and deliveringthem to a common integration stream
In a continuous integration pattern, every engineer
is responsible for delivering his/her own changes
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 12/21
12
ClearCase/UCM Fundamentals
UCM Objects
Activities
All changes (checkout and checkin) are associated with an
activity
Streams Configuration of branch on top of a foundation label
Support development isolation and collaboration
Baselines and Components
Manages version labels of components on an integrationstream
Projects
Collection of an integration stream, development streams,
related baselines and activities
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 13/21
13
ClearCase/UCM Fundamentals
Streams are Configurations
Streams serve two primary purposes Configure views attached to them
Store the activities that developers work on in their views
Foundation BaselineFoundation Baseline
Activity
Stream
VOB
Activity Activity
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 14/21
14
ClearCase/UCM Fundamentals
Streams: Baseline + Change
Streams encapsulatechanges to components Selects component
baselines
Two types of streams Development streams,
typically one per developer
Integration stream, for combining activities of all
developers and creatingnew baselines
Each development streamcreates a branch off thebaseline
Alpha BL Alpha BL11 Beta BLBeta BL11
Activity Activity
Activity
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 15/21
15
ClearCase/UCM Fundamentals
UCM Workflow
Develop
Integrate
Join a
Project
Make
Changes
Create
Baseline
Recommend
Baseline
Deliver
Changes
Build
Component
Rebase
Workspace
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 16/21
16
ClearCase/UCM Fundamentals
UCM Deliver
RELREL0303..0505 RELREL0303..0505
Defect 332Defect 551
Add Button Add Button
Development
StreamsIntegration
Stream
RELREL0303..0606
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 17/21
17
ClearCase/UCM Fundamentals
UCM Deliver Operation
Deliver preview allows visibility prior to
performing and actions
Automatically sets up merge context andinitiates merging if needed
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 18/21
18
ClearCase/UCM Fundamentals
UCM Deliver Operation
Can be cancelled, halted and resumed
All work checked out, complete operationchecks in all changes
Delivery activity automatically created
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 19/21
19
ClearCase/UCM Fundamentals
UCM Rebase
RELREL0303..0202 REL03.06REL03.06
Development
StreamsIntegration
Stream
RELREL0303..0606
Defect 332Defect 551
Add Button
Defect 332Defect 551
Add Button
Defect 41
8/6/2019 GeneralUCMPresentation
http://slidepdf.com/reader/full/generalucmpresentation 21/21
21
ClearCase/UCM Fundamentals
ben_garden viewbill_garden view
/garden_intg
Deliver y and Rebase
Changes are delivered to the
integration stream, and rebased on
other development streams
REL01
REL02
/ben_garden/bill_garden