Required BugIDs in API?

Post your questions regarding using the Vault and Fortress API in your programs.

Moderator: SourceGear

Post Reply
Steve.Czetty
Posts: 4
Joined: Fri Apr 11, 2008 2:38 pm

Required BugIDs in API?

Post by Steve.Czetty » Fri Apr 11, 2008 2:46 pm

I am working on an in-house application that needs to be integrated with Vault. All of our repositories require a BugID on checkin, but that does not seem to be enforced when I execute a checkin via ServerOperations.ProcessCommandCheckIn(). Do I need to enforce it via my application, or is there another API that I should use for this sort of operation?

Any help would be appreciated.

Steve Czetty
Programmer
IE Discovery, Inc.

shannon

Post by shannon » Fri Apr 11, 2008 3:13 pm

You'll need to check that yourself before calling a checkin or commit method.

ServerOperations.client.get_ClientInstance().get_TreeCache().get_RepositoryOptions().get_RequireBugID()
will tell you whether or not bugids are required.

Steve.Czetty
Posts: 4
Joined: Fri Apr 11, 2008 2:38 pm

Post by Steve.Czetty » Fri Apr 11, 2008 3:21 pm

Thanks a bunch!

One more question: is this behavior considered a feature or a bug? There is a single case where the bugID will not be necessary, so I don't want that case to mysteriously break after a server upgrade.
Steve Czetty
Programmer, Application Development Group
IE Discovery, Inc.

shannon

Post by shannon » Fri Apr 11, 2008 3:27 pm

We have no incentive to change it because all of our clients are designed that way.

Post Reply