The Vesta Approach to Software Configuration Management. Heydon, A., Levin, R., Mann, T., & Yu, Y. 2001.
The Vesta Approach to Software Configuration Management [link]Paper  abstract   bibtex   
Vesta is a system for software configuration management. It stores collections of source files, keeps track of which versions of which files go together, and automates the process of building a complete software artifact from its component pieces. Vesta\textquoterights novel approach gives it three important properties. First, every build is repeatable, because its component sources and build tools are stored immutably and immortally, and its configuration description completely specifies what components and tools are used and how they are put together. Second, every build is incremental, because results of previous builds are cached and reused. Third, every build is consistent, because all build dependencies are automatically captured and recorded, so that a cached result from a previous build is reused only when doing so is certain to be correct. In addition, Vesta\textquoterights flexible language for writing configuration descriptions makes it easy to describe large software configurations in a modular fashion and to create variant configurations by customizing build parameters. This paper gives a brief overview of Vesta, outlining Vesta\textquoterights advantages over traditional tools, how those benefits are achieved, and the system\textquoterights overall performance.
@booklet {Heydon01thevesta,
	title = {The Vesta Approach to Software Configuration Management},
	year = {2001},
	abstract = {Vesta is a system for software configuration management. It stores collections of source files, keeps track of which versions of which files go together, and automates the process of building a complete software artifact from its component pieces. Vesta{\textquoteright}s novel approach gives it three important properties. First, every build is repeatable, because its component sources and build tools are stored immutably and immortally, and its configuration description completely specifies what components and tools are used and how they are put together. Second, every build is incremental, because results of previous builds are cached and reused. Third, every build is consistent, because all build dependencies are automatically captured and recorded, so that a cached result from a previous build is reused only when doing so is certain to be correct. In addition, Vesta{\textquoteright}s flexible language for writing configuration descriptions makes it easy to describe large software configurations in a modular fashion and to create variant configurations by customizing build parameters. This paper gives a brief overview of Vesta, outlining Vesta{\textquoteright}s advantages over traditional tools, how those benefits are achieved, and the system{\textquoteright}s overall performance.},
	url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.23.7370},
	author = {Allan Heydon and Roy Levin and Timothy Mann and Yuan Yu}
}
Downloads: 0