Invalid Option VcsException for Perforce - p4 changes command?

I'm just starting out with TeamCity and am having trouble gettings it to work on my local machine, using the perforce project VCS roots.

I believe I have everything configured correctly (i.e. When I "Test Connection" it says everything is working), however when I run the build I get a VCSException. Here are the details:

Usage: changes Invalid option: -t.
jetbrains.buildServer.vcs.VcsException: Usage: changes
Invalid option: -t.

at jetbrains.buildServer.buildTriggers.vcs.perforce.PerforceConnection.runCommand(
at jetbrains.buildServer.buildTriggers.vcs.perforce.PerforceConnection.runChangesCommand(
at jetbrains.buildServer.buildTriggers.vcs.perforce.PerforceConnection.addChanges(
at jetbrains.buildServer.buildTriggers.vcs.perforce.PerforceSupport.collectBuildChanges(
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(
at jetbrains.buildServer.serverSide.impl.ProjectImpl.loadChanges(
at jetbrains.buildServer.serverSide.impl.ProjectImpl.checkForModifications(
at jetbrains.buildServer.serverSide.impl.BuildServerImpl.checkForModifications(
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$2.doSomething(
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$

My Diagnosis
It looks like its trying to run a p4 changes command with an invalid -t parameter. I can replicate the error locally running p4 by typing the following:

> p4 changes -t
Which gives me:
*Usage: changes
Invalid option: -t.*

Any idea what might be causing this? I just updated my p4 client, but our server is quite a bit older. Either way, I can't find anything in the current documentation of p4 changes about a -t parameter, and in any case, I figured the p4 client would determine which command line options were valid.

Relevant Versions

  • TeamCity Version 1.0-beta build 1492

  • Perforce Client: Rev. P4/NTX86/2006.1/104197 (2006/07/28)

  • Perforce Server: Server 2002.2/52749

Update: After further testing, it appears this doesn't completely stop the build, and my buildagent does correctly pull down the files. Unsure what practical affect this has, other than a big red warning label.

Message was edited by:

Please sign in to leave a comment.