Printrak_ClearCase_Training_Class.ppt

Motorola Internal Use Only Copyright - July 2002 7/4/2002 Michael Harris - Motorola Internal Use Only Copyright - July 2002 ClearCase Fundamentals Training for Printrak Contents Part 1 – What is ClearCase? Part 2 – Introducing the tools. Part 3 – Version Controlling an Element Part 4 – Finding your way Part 5 – Pulling it all together Part 6 – Developer Selects the Path Part 7 – Another Assignment using a Snapshot View. Part 8 – We have more to do. Part 9 – Release Manger Creates a Integration Release Label Part 10 – Developers can now refer to the view profile checkpoints Part 11 – Folders as Elements References Part 1 - What Is ClearCase? Version Control/Configuration Management (VOBs) Workspace Management (Views) Build Management (clearmake, omake, or clearaudit) Process Enforcement (triggers) What am I going to Learn ? What is ClearCase – Views and Vobs ? What is our Development Process ? How do I create or Modify files ? What is a Branch and When do I use them? How do I get my changes integrated? How do I get code built? How do I fix mistakes ? Applix/ClearCase Development Path Applix/ClearCase Development Path Applix/ClearCase Development Path Basic Usage Model What Is a VOB? A VOB is a: Read-only repository of ClearCase elements Network-wide file system resource which stores version-controlled data What is an Element ? What is an Element Version Tree ? Version-Extended Names Enables you to specify a version that may not be visible in your dynamic view @@ (extended-naming symbol) denotes a path into the version tree of an element Specific integer versions hello.c@@\main\3 User-defined version labels hello.c@@\IKNT_5.0.18 Special ClearCase-maintained labels hello.c@@\main\LATEST Using Version-Extended Names Using a standard name, you access the version of the file that your dynamic view selects: M:\MHARRIS2_view\project_hw\srctype hello.c #include hello.h int main() { printf(Hello, %s!\n, env_user() ); printf(Your home folder is