[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Obtaining the files modified/created after a failed/successful build

From: Todd Denniston
Subject: Re: Obtaining the files modified/created after a failed/successful build of CVS repository
Date: Wed, 20 Aug 2008 10:11:16 -0400
User-agent: Thunderbird (X11/20080707)

Gaurav Chhabra wrote, On 08/20/2008 09:38 AM:

We are using NetBeans for connecting to CVS and we are also using Cruise
Control for automating build process. I want to know if there is any way
through which I can come to know about the files that have been
modified/created after a build has failed/succeeded.

Are you talking about current situation or the future?
For the future, I would suggest having Cruise Control start apply a tag[1] to what it checks out and builds.

For the past... cvs2cl and a bit of thinking on what date strings to use to apply tags.

 Some command that I can
run on the whole CVS repository that may provide me with the desired

cvs2cl[2] will help a lot, but with out tags, the info it gives you will be harder to use.
My favorite method of using it is: `cvs2cl -r -t`

Though there is a cruise control log file that states everything but getting
only the required data from that log file will be akin to searching a needle
in a haystack.

I fear with out tags finding the info from CVS will be similar.

[1] Not a single tag, but give CC a way to build a tag that the humans will A) know is CC's tag, B) be able to figure out applies to which build.
A simplistic method to make the tag would be (in bash)
export ThisCCTag=CC_`date +%Y%m%d%H%M`
or if you need more resolution :)
export ThisCCTag=CC_`date +%Y%m%d%H%M%S%N`

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]