IBM Software Group Rational software IBM Software

IBM Software Group Rational software ® IBM Software Group Building a Distributed Release Process Using IBM Rational Clear. Case, IBM Rational Clear. DDTS at Cisco Systems Rinat Ailon and Gadi Berman Cisco Systems rgoren@cisco. com gberman@cisco. com SCMA 45

Rational User Conference 2003 Group IBM Software Rational software ®

Rational User Conference 2003 Group IBM Software Rational software Who Are We? A release engineering team in Cisco Systems (15 release engineers), that provides process and tools for a distributed development and test environments (1800 engineers in 10 sites) ®

Rational User Conference 2003 Group IBM Software Rational software Specifically, we handle § Change Management § Build Management In a distributed environment, using § IBM Rational Clear. Case § IBM Rational Clear. DDTS § IBM Rational Clear. Case Multi. Site ®

Rational User Conference 2003 Group IBM Software Rational software Products are built in 5 sites (SJ, Champaign, Netanya, Bangalore, Chennai) Builds should be monitored and controlled from all sites (mutually) Redundancy is needed for fast recovery Total of 100 different products/releases/platforms builds on 30 build machines, used by 10 development sites. Build machines should be protected ®

Rational User Conference 2003 Group IBM Software Rational software The strategy The tools ®

Rational User Conference 2003 Group IBM Software Rational software ®

Rational User Conference 2003 Group IBM Software Rational software Getting There Release Engineering Team Release Management PIT Development Teams Test Teams ®

Rational User Conference 2003 Group IBM Software Rational software The PIT – a cross organizational Process Improvement Team was established The PIT includes developers, test engineers, team leaders, and a project manager, all working together to improve the release engineering process ®

Rational User Conference 2003 Group IBM Software Rational software PIT Baseline Deliverables Mapping the current process that is used ("is model"), and then identify the gaps, if exist, to a "should model" that would address better and improve team operations Identifying our release engineering challenges/problems Identifying the “should model” RE meta-process Identifying the “should model” RE process boundaries Defining the sub processes and provide requirements documents ®

Rational User Conference 2003 Group IBM Software Rational software Identifying The RE Meta-Process ®

Rational User Conference 2003 Group IBM Software Rational software Identifying The RE Process Boundaries ®

Rational User Conference 2003 Group IBM Software Rational software Defining The Sub Processes Daily/Weekly Build Process We have defined our current daily/weekly build process in terms of ownerships/responsibilities, occurrences, schedules, inputs, outputs, and customers ®

Rational User Conference 2003 Group IBM Software Rational software Once the current process is defined, we can start working on improving it ®

Rational User Conference 2003 Group IBM Software Rational software ®

Rational User Conference 2003 Group IBM Software Rational software Change Management Improved Process Developers work on private or shared branch (per task/ddts item) Work is merged by developers (push) to the daily branch, where the integration (daily) build is performed Official Integ Private Shared Work is merged by the project manager (pull) to the official (weekly) branch, where the official (weekly) build is performed ®

Rational User Conference 2003 Group IBM Software Rational software Build Improved Process The second phase was to improve the build tools, so it will align with the change management process and will provide a solution to our needs ®

Rational User Conference 2003 Group IBM Software Rational software ®

Rational User Conference 2003 Group IBM Software Rational software From Process To Tools Build Management Change Management Quality Assessment ®

Rational User Conference 2003 Group IBM Software Rational software Change Management Process Support Tool We have developed a tool and a concept designed to deploy our change management methodologies and make Rational Clear. Case operations simpler ®

Rational User Conference 2003 Group IBM Software Rational software MATIS Clear. Case Manager 3. 3 At a glance … ®

Rational User Conference 2003 Group IBM Software Rational software MCCM 3. 3 Example Operation – Create View Choose the profile to work with Choose dynamic or snapshot view In a snapshot view you may add the load rules here. Use the “Add” and “Remove” buttons to edit the list of directories to load into the snapshot view What is a profile? A profile is a shared branching scheme which the view is based on. By creating the view based on a profile – we do not need to know how to create config specs. ®

Rational User Conference 2003 Group IBM Software Rational software MCCM 3. 3 Example Operation - Merge Choose branch to merge from. Only the important branches are shown. Choose view to merge to. and then … ®

Rational User Conference 2003 Group IBM Software Rational software Merge Choose in which directory you want to look for files that need merging. and then … ®

Rational User Conference 2003 Group IBM Software Rational software Rational Clear. Case Merge Manager Will Appear With The List Of Relevant Files: ®

Rational User Conference 2003 Group IBM Software Rational software Sites With No Rational Clear. Case Servers Site with no Rational Clear. Case servers, use Rational Clear. Case Web interface ®

Rational User Conference 2003 Group IBM Software Rational software MATIS Build System is a generic build framework that can wrap any type of build architecture and provides: § Web interface for scheduling, controlling and monitoring builds § Log parser for easy lookup and messaging of errors § Builds related reporting system § Protects build machines and provides redundancy between machines ®

Rational User Conference 2003 Group IBM Software Rational software Build Control Center Start/Stop/Continue/ Rerun builds Schedule builds Monitor running builds ®

Rational User Conference 2003 Group IBM Software Rational software Official Build. Board Public board to hold official builds for a product to be downloaded ®

Rational User Conference 2003 Group IBM Software Rational software Build Reports Reporting on changes made between two builds and changes made from a certain build to the upcoming build ®

Rational User Conference 2003 Group IBM Software Rational software Quality Metric Graphs System Displays the current status of a product’s quality during the development cycle ®

Rational User Conference 2003 Group IBM Software Rational software Quality Metric Graphs system Displays the trend of a product’s quality during the development cycle ®

Rational User Conference 2003 Group IBM Software Rational software ®

Rational User Conference 2003 Group IBM Software Rational software Gadi Berman gberman@cisco. com Rinat Ailon rgoren@cisco. com ®