1 / 35

Rinat Ailon and Gadi Berman Cisco Systems rgoren@cisco gberman@cisco

Building a Distributed Release Process Using IBM Rational ClearCase, IBM Rational ClearDDTS at Cisco Systems. Rinat Ailon and Gadi Berman Cisco Systems rgoren@cisco.com gberman@cisco.com. Who are we?.

barb
Download Presentation

Rinat Ailon and Gadi Berman Cisco Systems rgoren@cisco gberman@cisco

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Building a Distributed Release Process Using IBM Rational ClearCase, IBM Rational ClearDDTS at Cisco Systems Rinat Ailon and Gadi Berman Cisco Systems rgoren@cisco.com gberman@cisco.com SCMA45

  2. Who are we?

  3. 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) Who Are We?

  4. Specifically, we handle • Change Management • Build Management • In a distributed environment, using • IBM Rational ClearCase • IBM Rational ClearDDTS • IBM Rational ClearCase MultiSite

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

  6. The strategy • The tools

  7. The Strategy How?

  8. Development Teams Release Engineering Team Test Teams Getting There Release Management PIT

  9. The PIT • 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

  10. 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

  11. Identifying The RE Meta-Process

  12. Identifying The RE Process Boundaries

  13. 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

  14. Once the current process is defined, we can start working on improving it

  15. Process

  16. Integ Official Shared Private 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 • Work is merged by the project manager (pull) to the official (weekly) branch, where the official (weekly) build is performed

  17. 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

  18. Tools

  19. Build Management Change Management Quality Assessment From Process To Tools

  20. Change Management Process Support Tool • We have developed a tool and a concept designed to deploy our change management methodologies and make Rational ClearCase operations simpler

  21. MATIS ClearCase Manager3.3 At a glance …

  22. MCCM3.3 Example Operation – Create View Choose the profile to work with 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. 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

  23. MCCM3.3 Example Operation - Merge Choose branch to merge from. Only the important branches are shown. Choose view to merge to. and then …

  24. Merge Choose in which directory you want to look for files that need merging. and then …

  25. Rational ClearCase Merge Manager Will Appear With The List Of Relevant Files:

  26. Sites With No Rational ClearCase Servers • Site with no Rational ClearCase servers, use Rational ClearCase Web interface

  27. MATIS Build System • 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

  28. Schedule builds Start/Stop/Continue/Rerun builds Monitor running builds Build Control Center

  29. Official BuildBoard Public board to hold official builds for a product to be downloaded

  30. Build Reports Reporting on changes made between two builds and changes made from a certain build to the upcoming build

  31. Quality Metric Graphs System • Displays the current status of a product’s quality during the development cycle

  32. Quality Metric Graphs system • Displays the trend of a product’s quality during the development cycle

  33. DEMO

  34. QUESTIONS

  35. Thank You Gadi Berman gberman@cisco.com Rinat Ailon rgoren@cisco.com

More Related