1 / 8

Elements of the Enterprise CC Environment

Elements of the Enterprise CC Environment. Parallel Development Multiple supported releases and features Rapidly changing development strategies Support concerns can limit software tool options Source control tools cannot impede development. Some Ideas on Best Practices.

beck
Download Presentation

Elements of the Enterprise CC Environment

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. Elements of the Enterprise CC Environment • Parallel Development • Multiple supported releases and features • Rapidly changing development strategies • Support concerns can limit software tool options • Source control tools cannot impede development

  2. Some Ideas on Best Practices • Repeatability, both from a procedural and organizational standpoint • “No such thing as a silver bullet.” • Automation should center on • Simplifying developer’s jobs without sacrificing administrative control & flexibility • Making software development more visible • Reducing admin time spent on common tasks

  3. Simplifying User Administration • A config spec generator can replace some features of UCM • Keeps config spec in a group-readable, admin-writable directory • Automatically creates development branches in the VOBs • Automatically creates config spec based on branching scheme

  4. Simplifying User Administration • A wrapper for mkview • NIS host map entries for vws_<username>, pointing to view server (either central server or user’s workstation) • mkview script creates view in a view_storage directory on vws_<username>. • Easy to modify view server parameters (location, cache, etc.)

  5. Watching MultiSite • Script monitors the size of the incoming and outgoing shipping directories. • Notified daily if there are failed packet deliveries

  6. Homebrew Product Integration • ClearQuest 2001 / ClearCase 4.1 integration is nice, but slow • To avoid overhead due to authentication, Rational developers decided to hold client license for 90 minutes. No way to change timeout period. • “The gods are just, and of our pleasant vicesMake instruments to plague us.” -- King Lear, V. iii • Rational’s suggestion: buy as many CQ licenses as CC licenses.

  7. Upside / Downside • Faster connection for checkins and checkouts • No license usage • No ClearQuest DB storage yet (working on database structures) • Need to use cqperl (Perl 5.6) to use Win32::ODBC library

  8. A final tip • When moving a VOB from Windows NT to Windows 2000-- • fix_prot (it’s in the CCHOME/etc/utils directory) the VOBs and views • fix_prot -r -root -chown <owner> -chgrp <group> <storage directory> • cleartool protectvob the VOBs • Reboot clients and server to restart MVFS (because it’s a Windows driver)

More Related