Perforce plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Perforce plugin

citron
Hi,
 
I have a question regarding the Perforce plugin.
 
How do I configure it to sync to a specific label?
 
Thanks for any help.
 
Regards,
Anders

Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it!
Reply | Threaded
Open this post in threaded view
|

Re: Perforce plugin

bwestrich
Though I haven't tested it, I believe you could just put the label
name at the end of the depot path.

e.g.  //mydepot/myproject/...@mylabel

If you find this works, let us know and we can add this example to the
on-line help.

If you find this doesn't work, let us know too.  :-)


On Nov 28, 2007 8:22 AM, Anders Viklund <[hidden email]> wrote:

>
>  Hi,
>
> I have a question regarding the Perforce plugin.
>
> How do I configure it to sync to a specific label?
>
> Thanks for any help.
>
> Regards,
> Anders
> ________________________________
> Invite your mail contacts to join your friends list with Windows Live
> Spaces. It's easy! Try it!

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Perforce plugin

citron
Hi Brian,
 
I have just tested to append the label to the Depot Path, but I get this error message in the configuration tab:
 
Path must end with Perforce wildcard: '/...' (Example: //depot/ProjectName/...)
 
and this error message in the console:
 
Caught Exception communicating with perforce. Error in client specification. Error detected at line 9. Revision chars (@,#) not allowed in [hidden email].
 
 


> Date: Wed, 28 Nov 2007 10:00:45 -0600
> From: [hidden email]
> To: [hidden email]
> Subject: Re: Perforce plugin
>
> Though I haven't tested it, I believe you could just put the label
> name at the end of the depot path.
>
> e.g. //mydepot/myproject/...@mylabel
>
> If you find this works, let us know and we can add this example to the
> on-line help.
>
> If you find this doesn't work, let us know too. :-)
>
>
> On Nov 28, 2007 8:22 AM, Anders Viklund <[hidden email]> wrote:
> >
> > Hi,
> >
> > I have a question regarding the Perforce plugin.
> >
> > How do I configure it to sync to a specific label?
> >
> > Thanks for any help.
> >
> > Regards,
> > Anders
> > ________________________________
> > Invite your mail contacts to join your friends list with Windows Live
> > Spaces. It's easy! Try it!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



Discover the new Windows Vista Learn more!
Reply | Threaded
Open this post in threaded view
|

Re: Perforce plugin

bwestrich
This error is happening because the Perforce workspace created by
Hudson is attempting to use the label in the Perforce workspace view.
You can resolve it by creating the perforce workspace yourself (vs.
having Hudson create it). This is done by unchecking the option
'Let Hudson Manage Workspace View'.  After doing this, you'd still
need to specify the label at the end of the depot path (in the Hudson
config page).

You can safely ignore the message ">  Path must end with Perforce
wildcard: '/...' (Example:
> //depot/ProjectName/...)".  This is informational only.  If the approach I've sketched out above works for using Perforce labels, we may want to consider removing this check.

Hopefully the above approach will work for you. Let us know how it goes...

On Nov 28, 2007 10:15 AM, Anders Viklund <[hidden email]> wrote:

>
>  Hi Brian,
>
>  I have just tested to append the label to the Depot Path, but I get this
> error message in the configuration tab:
>
>  Path must end with Perforce wildcard: '/...' (Example:
> //depot/ProjectName/...)
>
>  and this error message in the console:
>
>  Caught Exception communicating with perforce. Error in client
> specification. Error detected at line 9. Revision chars (@,#) not allowed in
> '//depot/...@label1'.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Perforce plugin

citron
By unchecking the 'Let Hudson Manage Workspace View' option then the label can be added to the Depot Path.
But, it will only sync to the Head revision, no matter which label is beeing used. 
It seems like it does not care about the label (as long as it exists in Perforce).
 

> Date: Wed, 28 Nov 2007 10:32:02 -0600
> From: [hidden email]
> To: [hidden email]
> Subject: Re: Perforce plugin
>
> This error is happening because the Perforce workspace created by
> Hudson is attempting to use the label in the Perforce workspace view.
> You can resolve it by creating the perforce workspace yourself (vs.
> having Hudson create it). This is done by unchecking the option
> 'Let Hudson Manage Workspace View'. After doing this, you'd still
> need to specify the label at the end of the depot path (in the Hudson
> config page).
>
> You can safely ignore the message "> Path must end with Perforce
> wildcard: '/...' (Example:
> > //depot/ProjectName/...)". This is informational only. If the approach I've sketched out above works for using Perforce labels, we may want to consider removing this check.
>
> Hopefully the above approach will work for you. Let us know how it goes...
>
> On Nov 28, 2007 10:15 AM, Anders Viklund <[hidden email]> wrote:
> >
> > Hi Brian,
> >
> > I have just tested to append the label to the Depot Path, but I get this
> > error message in the configuration tab:
> >
> > Path must end with Perforce wildcard: '/...' (Example:
> > //depot/ProjectName/...)
> >
> > and this error message in the console:
> >
> > Caught Exception communicating with perforce. Error in client
> > specification. Error detected at line 9. Revision chars (@,#) not allowed in
> > '//depot/...@label1'.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



Discover the new Windows Vista Learn more!
Reply | Threaded
Open this post in threaded view
|

Re: Perforce plugin

bwestrich
Mike,

Anders' issue (of the plugin not using labels) may be related to
p4_java.  I noticed some code in Workspaces.java that appears to
ignore the presence of labels in filespecs...

        public StringBuilder syncToHead(String path, boolean forceSync)
throws PerforceException {
                if(!path.endsWith("#head")) {
                        path += "#head";
                }

I'm not sure why this if statement is needed.  When I comment it out,
the plugin appears to work with labels (in my limited testing).

Your thoughts?

Brian

On Nov 28, 2007 12:21 PM, Anders Viklund <[hidden email]> wrote:

>
>  By unchecking the 'Let Hudson Manage Workspace View' option then the label
> can be added to the Depot Path.
>  But, it will only sync to the Head revision, no matter which label is
> beeing used.
>  It seems like it does not care about the label (as long as it exists in
> Perforce).
>
>
> > Date: Wed, 28 Nov 2007 10:32:02 -0600
>
> > From: [hidden email]
> > To: [hidden email]
> > Subject: Re: Perforce plugin
> >
>
> > This error is happening because the Perforce workspace created by
> > Hudson is attempting to use the label in the Perforce workspace view.
> > You can resolve it by creating the perforce workspace yourself (vs.
> > having Hudson create it). This is done by unchecking the option
> > 'Let Hudson Manage Workspace View'. After doing this, you'd still
> > need to specify the label at the end of the depot path (in the Hudson
> > config page).
> >
> > You can safely ignore the message "> Path must end with Perforce
> > wildcard: '/...' (Example:
> > > //depot/ProjectName/...)". This is informational only. If the approach
> I've sketched out above works for using Perforce labels, we may want to
> consider removing this check.
> >
> > Hopefully the above approach will work for you. Let us know how it goes...
> >
> > On Nov 28, 2007 10:15 AM, Anders Viklund <[hidden email]>
> wrote:
> > >
> > > Hi Brian,
> > >
> > > I have just tested to append the label to the Depot Path, but I get this
> > > error message in the configuration tab:
> > >
> > > Path must end with Perforce wildcard: '/...' (Example:
> > > //depot/ProjectName/...)
> > >
> > > and this error message in the console:
> > >
> > > Caught Exception communicating with perforce. Error in client
> > > specification. Error detected at line 9. Revision chars (@,#) not
> allowed in
> > > '//depot/...@label1'.
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> ________________________________
> Discover the new Windows Vista Learn more!

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]