Neil, I'm the Perforce SCM plugin author. Perhaps I need to explain why
the Perforce SCM plugin is doing what it is doing.
Continuum needs to check out a project's source into a particular
working directory. Perforce does not have any notion of checkout to a
random directory - you need to use a clientspec to map a depot location
onto a local filesystem location and then sync that clientspec in order
to checkout. So when Continuum asks the plugin to checkout //depot/foo
to /tmp/working/bar, the plugin creates or updates a clientspec named
${user}-${host}-maven to have a Root of /tmp/working/bar with a View
mapping of //depot/foo/... to //${user}-${host}-maven/... and syncs
that.
The idea is that the user should not have to create any special build
clientspec - the plugin will handle all of that internally.
Obviously there is a bit of gum in the works. I'm planning on
installing Continuum today and trying out a build of my own to see if I
have any better luck. I'll let you know how I fare.
mike
-----Original Message-----
From: Neil Padgen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 13, 2005 4:52 AM
To: [email protected]
Subject: RE: Cannot add Perforce project to Continuum 1.0.2
> -----Original Message-----
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: 12 December 2005 17:57
> To: [email protected]
> Subject: Re: Cannot add Perforce project to Continuum 1.0.2
>
> In add pages, you must use http, https or ftp (and file if it's
> configured in application.xml) protocols. scm urls aren't valid urls.
Thanks Emmanuel. However, I now seem to be getting the same error as
Robert - "Provider message: Unable to sync".
Seems from the logs that it's forcing a Perforce client of
"nrp-pc-nrp-maven" (pc-nrp is my hostname). I need to be able to
specify a p4 username and p4 client for Continuum to use.
Usually specifying P4USER and P4CLIENT in the environment is enough.
Can this be done with Continuum?
-- Neil
