APT Configuration Management Jesse Doggett APT Configuration Management

  • Slides: 22
Download presentation
APT Configuration Management Jesse Doggett APT Configuration Management May 25 th, 2004

APT Configuration Management Jesse Doggett APT Configuration Management May 25 th, 2004

Outline for the Talk n What Is Configuration Management? n APT Development Challenges n

Outline for the Talk n What Is Configuration Management? n APT Development Challenges n APT CM Techniques n Conclusion APT Configuration Management May 25 th, 2004 2

Configuration Management n ANSI/EIA-649 u "A management process for establishing and maintaining consistency of

Configuration Management n ANSI/EIA-649 u "A management process for establishing and maintaining consistency of a product's performance, functional and physical attributes with its requirements, design and operational information throughout its life. " (http: //www. pdmic. com/cmic/introto. CM. shtml) n Susan Dart u "The goals of using CM are to ensure the integrity of a product and to make its evolution more manageable. ” (http: //www. loria. fr/~molli/cm-index. html) APT Configuration Management May 25 th, 2004 3

Tracking and Controlling Changed n A Little to a Lot u u None for

Tracking and Controlling Changed n A Little to a Lot u u None for My Web Page Extreme Tactics for All Aspects of Project Management APT Configuration Management May 25 th, 2004 4

APT Development Challenges n Code Integrity (Design, Implementation) n Multiple Developers (Implementation) n Build

APT Development Challenges n Code Integrity (Design, Implementation) n Multiple Developers (Implementation) n Build Availability (build, testing) n Release Requirements (release) APT Configuration Management May 25 th, 2004 5

More Challenges n Multiple Classes of Users (requiements, release) n Multiple Platforms (implement, build,

More Challenges n Multiple Classes of Users (requiements, release) n Multiple Platforms (implement, build, test, release) n Concurrent Release Development (implement, build, test) APT Configuration Management May 25 th, 2004 6

APT CM Practices n Good Design (design) n Uniform Build System (implement, build) n

APT CM Practices n Good Design (design) n Uniform Build System (implement, build) n Source Code Control (implement, build) n Automated Builds (build, test) APT Configuration Management May 25 th, 2004 7

More CM Practices n Install. Anywhere Installers Generator n Alpha/Beta/Candidate Versioning n Regularly Scheduled

More CM Practices n Install. Anywhere Installers Generator n Alpha/Beta/Candidate Versioning n Regularly Scheduled Releases n Documented Release Procedures APT Configuration Management May 25 th, 2004 8

APT Organization n Document Browser n Hierarchical Model for Documents n Generic Form &

APT Organization n Document Browser n Hierarchical Model for Documents n Generic Form & Spread. Sheet Editors n Plug-and-Play Editor Tools APT Configuration Management May 25 th, 2004 9

APT Configuration Management May 25 th, 2004 10

APT Configuration Management May 25 th, 2004 10

ANT Build System. n ANT is a Java Based Make-Like Utility n Incorporates Many

ANT Build System. n ANT is a Java Based Make-Like Utility n Incorporates Many File System Commands n Platform Independent n XML Build Files APT Configuration Management May 25 th, 2004 11

Simple ANT Buld File <project name=“myproject” default=“build” basedir=“. ”> <property name=“classes” value=“${basedir}/classes”/> <target name=“build”

Simple ANT Buld File <project name=“myproject” default=“build” basedir=“. ”> <property name=“classes” value=“${basedir}/classes”/> <target name=“build” depends=“init”> <java srcdir=“${basedir}” destdir=“${classes}”/> </target> target <target name=“init”> <mkdir dir=“${classes}”/> </target> target </project> project APT Configuration Management May 25 th, 2004 12

CVS Source Code Control n CVS Allows Source Code Sharing n Branch Tags for

CVS Source Code Control n CVS Allows Source Code Sharing n Branch Tags for Each Release u Isolate Code u Quick Fixes APT Configuration Management May 25 th, 2004 13

APT Configuration Management May 25 th, 2004 14

APT Configuration Management May 25 th, 2004 14

Installer. Anywhere n Install. Anywhere Automatically Builds Installers n Supports Multiple Platform Installers n

Installer. Anywhere n Install. Anywhere Automatically Builds Installers n Supports Multiple Platform Installers n Has a Graphical Interface to Define Projects n Installers Are Customizable n Batches Modes Available APT Configuration Management May 25 th, 2004 15

APT Configuration Management May 25 th, 2004 16

APT Configuration Management May 25 th, 2004 16

Nightly Builds. n Nightly Builds n Archived Weekly Builds n Develop and Delivery Branch

Nightly Builds. n Nightly Builds n Archived Weekly Builds n Develop and Delivery Branch Builds n Java. Doc API Documentation APT Configuration Management May 25 th, 2004 17

APT Release Scheme n α Alpha Releases n ß Beta Releases n Candidate Releases

APT Release Scheme n α Alpha Releases n ß Beta Releases n Candidate Releases n Bi-Monthly Operational Releases u Phase I, Phase II, Calibration, Hot APT Configuration Management May 25 th, 2004 18

Delivery APT n Documented Delivery Procedures a Must n Archiving n Quick Fixes n

Delivery APT n Documented Delivery Procedures a Must n Archiving n Quick Fixes n Patching: APTPatches. jar APT Configuration Management May 25 th, 2004 19

Main Strengths and Weaknesses n The latest develop version is always available. n Code

Main Strengths and Weaknesses n The latest develop version is always available. n Code for each release is isolated. n We are very robust to supporting multiple platforms. n We don’t have a good way to safely manage long term projects (> 2 months). APT Configuration Management May 25 th, 2004 20

Lessons Learned n Automate as much as possible. n Use existing proven tools Communicate

Lessons Learned n Automate as much as possible. n Use existing proven tools Communicate as much as possible. APT Configuration Management May 25 th, 2004 21

Conclusion: Top Practices n CVS Source Control n Nightly Builds n 3 rd Party

Conclusion: Top Practices n CVS Source Control n Nightly Builds n 3 rd Party Installer Generator www. stsci. edu/~doggett/cmtalk. html APT Configuration Management May 25 th, 2004 22