Editor's Blog
Scorch Update
A few customers have started adopting the scorch (wupdate
-C) command in their Continuous Integration (CI) processes and the numbers are
starting to come in. One customer reports their build time on one project
dropped from 76 minutes to 52 minutes, a 30% reduction. Their build pulls from
multiple snapshots, and the update from one snapshot dropped from about 10
minutes to under 10 seconds! If you haven't checked out scorch, what are you
waiting for? It is fast, it's robust, and uses fewer local and server resources
than a full check out.
This same customer reported one difference between scorch
and a remove + check out that led to an installation issue. The difference was
the time-stamps on the workspace files. Removing and checking out causes all
files to have the current time, while scorch doesn't change the time-stamp of
an existing file unless it is updated. When they packaged one such version
controlled file into an install image, that difference became visible.
At the moment, we haven't decided to do anything about that
difference, though we are considering adding touch functionality to
scorch, perhaps as an option. As a work-around if this affects only a few
files, I recommend removing or touching just the affected files before scorch
runs, which will force the time-stamp update of just those files.
Release Update
I had hoped to have an updated Product Line beta to announce
by now, but have had too many distractions to make the necessary progress. So I
will take this opportunity to highlight one fix in the most recent release. In
short, the Refresh Status command within the Visual Studio SnapshotCM
integration has been fixed. Most often the symptom was a disabled
Compare action icon/menu when wanting to review changes to a local file
(a good practice before checking in), even after selecting Refresh
Status.
Feedback Wanted
I recently visited a couple of long-time customers. My goal
was to solicit feedback on how they were using SnapshotCM, the performance they
were seeing, what they wanted/needed from SnapshotCM, etc. The feedback was
very valuable to me, and will be incorporated in changes you all will see in
the coming months. Yet, I always welcome additional feedback. So don't be shy -
I can't fix or improve what I don't know about. And the more customers I hear
from, the more clearly will be the priorities. So send me your thoughts
today!
Scott Kramer President support@truebluesoftware.com
|