1 / 4

Effective Version Management and Configuration Control Using CVS

This document outlines the principles of version management and configuration control, focusing on the Concurrent Versions System (CVS). It describes how CVS tracks file versions, facilitates multiple user access, and stores files in a repository on the CVS server. Readers will learn about the workflow of checking out files, making edits, committing changes, and updating local working directories. The guide also covers the structure of a JSOC repository, detailing key components such as application sources, library sources, and platform-specific binaries, as well as checking out various system configurations.

kurt
Télécharger la présentation

Effective Version Management and Configuration Control Using CVS

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. Source Code Version Management and Configuration Control Art Amezcua Status 11/5/2007

  2. Version Management and Configuration Control • CVS – Concurrent Versions System • Tracks versions of files • Allows multiple users • Files stored in “repository” on CVS server • Check-out files from repository into “working directory” (wd); edit wd files; commit changes to repository; update files in wd

  3. Version Management and Configuration Control • JSOC repository – make and base configuration files • base – application sources, library sources, scripts, documentation (including man pages) • build – icc/gcc wrappers • proj– application sources, library sources, scripts, documentation (including man pages) • projconf • su – Stanford-specific configuration • ex – external configuration • scripts, man, libs, bin – links to base and proj scripts, man pages, libraries, executables • <platform> – built platform-specific binaries

  4. Version Management and Configuration Control • Checking out systems • Base system: “cvs checkout DRMS” • Full JSOC system: “cvs checkout JSOC” • “cvs export DRMS” (tarball) • configure • Status • Repository structure final/stable • Source for JSOC’s active SUMS resides in “old” repository, “new” repository not tested • New repository SUMS needs minor ‘make’ and source changes prior to external distribution, plus testing

More Related