Kinook Software Forums

Go Back   Kinook Software Forums > Visual Build Professional > [VBP] Third Party Tools

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 09-16-2005, 06:00 PM
Chris Chris is online now
Registered User
 
Join Date: 08-30-2005
Posts: 2
Capturing output of Perforce changes cmd?

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
Reply With Quote
  #2  
Old 09-19-2005, 07:46 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,742
This should be automatic, just make sure 'Don't capture output' on the Global Options tab is unchecked.
Reply With Quote
  #3  
Old 09-19-2005, 02:46 PM
Chris Chris is online now
Registered User
 
Join Date: 08-30-2005
Posts: 2
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.
Reply With Quote
  #4  
Old 09-19-2005, 05:38 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,742
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.
Reply With Quote
  #5  
Old 01-12-2006, 02:59 PM
mseminatore mseminatore is online now
Registered User
 
Join Date: 09-14-2005
Posts: 17
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/...
Reply With Quote
  #6  
Old 01-12-2006, 06:01 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,742
//depot/some/path/...@[FormatDateP4("%LAST_BUILD_TIME%")],@now
[repeat with other paths as needed...]

http://www.perforce.com/perforce/doc...s.html#1048020
Reply With Quote
  #7  
Old 01-12-2006, 07:04 PM
mseminatore mseminatore is online now
Registered User
 
Join Date: 09-14-2005
Posts: 17
Where does FormatDateP4() come from. Is that new for 6.0a?
Reply With Quote
  #8  
Old 01-12-2006, 07:15 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,742
It's a project script function in the ContinuousIntegration.bld sample.
Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 10:39 PM.


Copyright 1999-2019 Kinook Software, Inc.