Capturing output of Perforce changes cmd?

[Chris]

Hi.

I'd like to capture the output of the Perforce "changes" cmd so I can include the changes since the last build in the build notification email sent at the end of the build.

I've tried to adapt some of the sample projects, but I haven't had much luck since I'm new to Visual Build Pro and VBScript.


Thanks,
--Chris

[kinook]

This should be automatic, just make sure 'Don't capture output' on the Global Options tab is unchecked.

[Chris]

Hi,

I wanted to do something like this in the build email:

The build completed successfully at 9/19/2005 12:32:13 PM on
the_build_machine.

These are the changes that went into the build
--------------------------------------------------------------

Change 4486 on 2005/09/16 15:24:24 by me@dev_machine 'Fixed problem'
Change 4485 on 2005/09/16 13:24:24 by someone@dev_machine 'Added menu item'


I want to capture just the output messages related to the changes.

[kinook]

If you store your last build date using vbld_FormatDateTime (see the 'Update build date' step in the ContinuousIntegration.bld sample), using a changes step like the one in that same sample ('Get changes') should do what you need.

[mseminatore]

What if we want to get changes on only part of the depot?

That sample assumes we want all changes for our current client spec which might map in a lot more than we are interested in. I tried to add this but the action seems to put the parameters in the wrong order.

What I tried was to add the file spec before the range info.

folders to process: //depot/project1/...

[kinook]

//depot/some/path/...@[FormatDateP4("%LAST_BUILD_TIME%")],@now
[repeat with other paths as needed...]

http://www.perforce.com/perforce/doc...s.html#1048020

[mseminatore]

Where does FormatDateP4() come from. Is that new for 6.0a?

[kinook]

It's a project script function in the ContinuousIntegration.bld sample.