How to tell whence check-in was made?

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

Moderator: SourceGear

Post Reply
Perry
Posts: 110
Joined: Tue Dec 27, 2005 9:11 am

How to tell whence check-in was made?

Post by Perry » Thu Jun 01, 2006 3:48 pm

Looking in history, it is not apparent to me to what machine checkouts were made, and from what machine checkins were made.

How can I tell if a given project has ever (or recently) been checked in from a particular client?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Thu Jun 01, 2006 4:10 pm

Checkout location is not shown in history. History only shows the username and any modifications to a file/folder, but has no specific client information.
Linda Bauer
SourceGear
Technical Support Manager

nevin
Posts: 10
Joined: Tue May 17, 2005 1:32 pm

Post by nevin » Thu Jun 15, 2006 5:51 am

actually I would find this really useful as well if this information was available.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Thu Jun 15, 2006 9:04 am

Before we would implement something like this, it would be helpful to know why you need this information.

There may be various ways of doing this, but it would depend on what problem you are trying to solve.
Linda Bauer
SourceGear
Technical Support Manager

Don Thimsen
Posts: 114
Joined: Fri Mar 05, 2004 11:18 am
Location: Raleigh, NC

Post by Don Thimsen » Thu Jun 15, 2006 10:16 am

Linda,

Just a guess, but it sounds like they want an audit trail for the physical machine that performs the check-in...

For something quick, how about adding IP address/Machine name to the email notification text in Vault???

Don

jclausius
Posts: 3702
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Thu Jun 15, 2006 10:57 am

Don Thimsen wrote:Just a guess, but it sounds like they want an audit trail for the physical machine that performs the check-in...
If that is the case, I would recomend putting the audit trail in the sgvault.log file.
Jeff Clausius
SourceGear

Post Reply