How to generate a CHANGELOG?

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Perry

How to generate a CHANGELOG?

Post by Perry » Wed Dec 22, 2004 6:00 pm

How can you make Vault generate a CHANGELOG (ie, output summaries of all changes -- or at least, all non-minor changes -- to a traditional CHANGELOG-style text file)?

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Wed Dec 22, 2004 11:03 pm

You can invoke a history query and then save it off using a few different formats, which could give you log info about what has changed.

Perry

re: CHANGELOG

Post by Perry » Thu Dec 23, 2004 12:36 pm

Ah, ok, thanks -- that sounds like a great start.

I would just need to find out how to do that from a commandline client, and then set that up to happen on some type of schedule (or is there a way to make it happen whenever there is a non-minor change?)

I admit, I was really hoping someone else who had already done this would helpfully post their already worked out answer :)

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Thu Dec 23, 2004 4:12 pm

The command line client will output history in XML format, so you'd need to do some post-processing on it to put it into a more easily readable format. Sorry we don't have anything set up already - maybe someone will post here if they have something you can use.

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Wed Dec 29, 2004 1:28 pm

This is a goal for me in the short term which, I want to post to my Vault API blog at http://weblogs.asp.net/jeremy_sheeley

When I get it done, I plan to check in the changes to add them to the command line client.

Post Reply