[JIRA] (JENKINS-29387) Cannot sync into workspaces with '@' in their path

2018-03-19 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-29387  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot sync into workspaces with '@' in their path   
 

  
 
 
 
 

 
 If you want to list changes limited by the 'view' of a client workspace use 'client syntax' e.g: 

 

changelist = p4.run( 'changes', '-m1', "//" + p4.getClientName() + "/..." ) 

 If you use the "//...@workspace" revision specifier then you are only listing the changes that are in the 'have' list for that workspaces.  If the workspace has never been synced then the have list will be empty and your script will have an empty array: java.lang.ArrayIndexOutOfBoundsException: 0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-29387) Cannot sync into workspaces with '@' in their path

2018-03-07 Thread jaysp...@amazon.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jay Spang commented on  JENKINS-29387  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot sync into workspaces with '@' in their path   
 

  
 
 
 
 

 
 Joel Brown I'm a bit reluctant to change a whole system property to fix this issue, but if Paul Allen says there's no easy way to do this with p4groovy, I'll definitely give that a try!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-29387) Cannot sync into workspaces with '@' in their path

2018-03-07 Thread jbr...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown commented on  JENKINS-29387  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot sync into workspaces with '@' in their path   
 

  
 
 
 
 

 
 Jay Spang you wrote "Jenkins appends '@2'  to the workspace" Does the above -Dhudson.slaves.WorkspaceList=_ help out as an alternative char to the "@"?  That should obviate the need for the escaping Paul did.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-29387) Cannot sync into workspaces with '@' in their path

2018-03-07 Thread jaysp...@amazon.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jay Spang commented on  JENKINS-29387  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot sync into workspaces with '@' in their path   
 

  
 
 
 
 

 
 Paul Allen sorry to bump a very old issue, but how can I use your fix when I'm using raw p4groovy to do more advanced stuff? I have a function called get_synced_changelist() that does exactly what the name implies. This code works fine except if the job runs on an executor other than 0. If that happens, Jenkins appends '@2'  to the workspace and p4groovy crashes when it tries to use that as the workspace root. Unless I'm missing something, I don't see any way to specify the client's root at the time of instantiation, so I don't know how to avoid this bug. Here's the code. The best way to repro this is to pin your job to a certain node, then Build it rapidly a few times (ensuring concurrent builds). Any build NOT on the first executor will fail.   def get_synced_changelist(String p4_credential_name, String client_name, String p4_stream) {     def ws = [$class: 'StreamWorkspaceImpl', charset: 'none', format: client_name, pinHost: false, streamName: p4_stream]     def p4 = p4(credential: p4_credential_name, workspace: ws) changelist = p4.run( 'changes', '-m1', "@"+ p4.getClientName() )     return changelist[0].change }   get_synced_changelist('p4tools', 'jenkins-${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}', '//depot/stream_name')          
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to