No Changelog Without Modificationset->Cvs
Chuck Burgess <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
Hello, In my builds, the *modificationset->cvs* piece takes an average of 90sec to run, which I'm pretty sure is due to its use of *cvs rlog* in combination with the horrendous number of branches that exist on this one large module that's being checked. This is my motivation for the next part... it's not the question. I had previously set the build to use a *cvsbootstrapper* to update the project sandbox, in combination with a *modificationset->filesystem *piece. Since a direct *cvs update* is immediate, it's obviously faster than the 90sec *cvs rlog* executions that I'm seeing. Combined that with the even faster results of the filesystem check for modifications, and this speeds my build queue up significantly. The cost, however, is that I lose the changelog info in the build results. The only changes shown are which files were touched... there is no "who changed it" paired with commit messages. This implies to me that the changelog info is captured by the * modificationset* piece of the build. Is there a way I can capture the changelog during the actual build itself, rather than in CC's *modificationset* check? I'd like to return to the *cvsbootstrapper + modificationset->filesystem* setup while still being able to show the CVS changelog info in the build results. Anyone dealt with this before? -- CRB ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Cruisecontrol-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user