CM Crossroads bills
itself as the worlds largest online community and resource center
for configuration management. CM Crossroads hosts
interactive discussion forums, a book store, a monthly
newsletter, Career Search and Jobs Board, an extensive library of
resource links a user contributed file cabinet and the
Configuration Management Body of Knowledge (CMBoK). The only down-side
is that they are funded by advertising, and as a result, open
source alternatives are rarely mentioned. With rare exceptions,
don't mention any OSS VC/SCM other than CVS.
- The
Trouble with Hidden Make Targets
- A nasty trap for the
unwary that can cause make(1) to report odd errors, stops
the -n option from working and prevents speedy parallel Make. It
can even cause Make to do the wrong work and update an up-to-date
file.
- Setting
a Makefile variable from outside the Makefile
- It's common
to have options in a Makefile that you alter when you start a
build. Perhaps the most common is a DEBUG option used to specify
whether the build you are doing creates debuggable or release
code.
The relevance for Aegis users is that this can be
automated by different integration_build_command and
build_command fields of the project configuration file.
-
Source Control HOWTO
- Our universities don't teach people
how to do source control. Our employers don't teach people how
to do source control. SCM tool vendors don't teach people how to
do source control. We need some materials that explain how
source control is done. My goal for this series of articles is
to create a comprehensive guide to help meet this need.
(Part 1, What
is Source Control?; Part 2, A Tale of Two
Trees; Part 3, Checkins;
Part 4, File
Merge)
- Making
Incremental Integration Work for You
- Integrating a change
at a time needs a tool which supports change sets. More than
that, it must support incremental development environments,
incremental impact analysis and the ability to roll back changes
easily.
- The Role
of Incremental Integration in a Parallel Development
Environment
- Team software development is a reality
because one person cannot develop todays complex software
applications in a timely manner. One of the greatest challenges
of team software development is integrating the changes made by
several developers, each completing coding tasks in an isolated
environment.
-
Approaching Continuous Integration
- The term continuous
integration is getting a bit of attention these days. It refers
to the process of integrating often (or immediately) to reduce
integration effort, complexity, and pain and to make changes more
readily available to others.