Elements of the Enterprise CC Environment

8
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

description

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. - PowerPoint PPT Presentation

Transcript of Elements of the Enterprise CC Environment

Page 1: 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

Page 2: Elements of the Enterprise CC Environment

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

Page 3: Elements of the Enterprise CC Environment

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

Page 4: Elements of the Enterprise CC Environment

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

Page 5: Elements of the Enterprise CC Environment

Watching MultiSite

• Script monitors the size of the incoming and outgoing shipping directories.

• Notified daily if there are failed packet deliveries

Page 6: Elements of the Enterprise CC Environment

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.

Page 7: Elements of the Enterprise CC Environment

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

Page 8: Elements of the Enterprise CC Environment

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)