Archive for category CMCrossroads

Common Interface

After much deliberation and soul searching I’ve finally decided it’s time to address one of my all time bugbears. I am going to develop a set of transferable libraries for analysing and operating a CMS. And because I am most familiar with Perl (and, as explained in my earlier post Glue Software, I find it [...]

,

1 Comment

Glue Software

As someone who inevitably becomes involved in the technical implementation of configuration management systems (CMS) I am often called upon to create what I choose to call ‘glue software’. Glue software is not a full integration between two products (often there is simply no way to fully integrate products) but rather it is a more [...]

1 Comment

Holographic Configuration Management

The advent of the ‘cloud’ and the idea of massively distributed systems (think grid computing and SaaS) is the latest technology swing with the potential to impact configuration management practice. I say ‘potential’ because a properly designed and implemented configuration management system will be able to copy without too much difficulty. The main impact will be [...]

,

1 Comment

The virtue of indolence

It has long appeared to me that people see virtue in making work. I see virtue in laziness. Or rather, I see virtue in eliminating work. As a freelancers I see part if my role on an contract as eliminating as much of the purpose for my presence as possible. This means optimizing away my [...]

,

Leave a Comment

Subversion’s Ignore List

The idea behind the Subversion ignore list is very simple: when adding (using svn add or svn import) files into a Subversion repository, any file that matches a pattern on the ignore list is skipped. The ignore list is constructed from two sources: the client specific global-ignores list; any svn:ignore property associated with the directory [...]

, , , ,

Leave a Comment

Labels versus Baselines

A common question from new Configuration Managers is, “What is the difference between a label and a baseline”. A label is exactly what it sounds like, a name assigned to one or more things (whatever they are). Generally no further qualification is needed. A baseline, in configuration management circles, has much more significance. A baseline [...]

,

1 Comment

Stubbing in build processes

When developing systems of any size the development team inevitably encounters the following problem. The developers of one sub-system need access to functionality to be provided by another, but the second sub-system is not in a position to provide the functionality and probably will not be for some time. When this happens it is common [...]

, ,

Leave a Comment

Stabilizing builds

One challenge facing build managers is how to control the environment in which builds are performed. How to ensure that each repeated build uses the same sources, the same libraries, the same compilers, and so on. Only by ensuring all these elements can we truly claim to be able to reproduce a build reliably and [...]

,

Leave a Comment

Creating Tags in Subversion

Subversion does not support labels as many version control tools do. Instead Subversion uses the svn copy command to create ‘tags’. By convention a Subversion repository is often divided into three sub-directories; trunk, where the main development is often (though not necessarily) done; branches, where (unsurprisingly) we maintain branches that may be used for any [...]

, ,

2 Comments

Differentiating Configuration Items from Components

Configuration management literature is replete with references to something called a ‘configuration item’ and most attempt to explain what a configuration item is. Despite this there remains confusion. “Should all files in my software system be a configuration item?” is a common enough question to raise concern that the concept of configuration item is not [...]

,

Leave a Comment

Follow

Get every new post delivered to your Inbox.