[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin

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


 
 
 
 

 
 
 

 
   
 Paul Allen closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing Duplicate Issue; reproduced and written test for JENKINS-50393, fix to follow.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50441  
 
 
  p4sync with default client name fails with latest version of p4 plugin   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin

2018-03-27 Thread mr...@sjm.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Rose updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50441  
 
 
  p4sync with default client name fails with latest version of p4 plugin   
 

  
 
 
 
 

 
Change By: 
 Michael Rose  
 

  
 
 
 
 

 
 This used to work:{quote}p4sync credential: 'p4integ.prod',   populate: previewOnly(quiet: true, pin: env.latest_version),   source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote} {{ ... p4 client -o jenkins-master- {color:#14892c} scm- promote{color}_ansible_playbooks promote_ansible_playbooks -0 + }}  {{ ... p4 client -i + }}  {{ P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. }}  {{ Mapping '//jenkins-master- {color:#d04437} scm/ promote{color}_ansible_playbooks promote_ansible_playbooks -0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'. }}  {quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin

2018-03-27 Thread mr...@sjm.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Rose updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50441  
 
 
  p4sync with default client name fails with latest version of p4 plugin   
 

  
 
 
 
 

 
Change By: 
 Michael Rose  
 

  
 
 
 
 

 
 This used to work:{quote}p4sync credential: 'p4integ.prod',   populate: previewOnly(quiet: true, pin: env.latest_version),   source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote}{{... p4 client -o jenkins-master - {color:#14892c}scm-promote{color}_ansible_playbooks-0 +}}{{ ... p4 client -i +}}{{ P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.}}{{ Mapping '//jenkins-master-{color:# ff d04437 }scm/promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.}}{quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you

[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin

2018-03-27 Thread mr...@sjm.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Rose updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50441  
 
 
  p4sync with default client name fails with latest version of p4 plugin   
 

  
 
 
 
 

 
Change By: 
 Michael Rose  
 

  
 
 
 
 

 
 This used to work:{quote}p4sync credential: 'p4integ.prod',   populate: previewOnly(quiet: true, pin: env.latest_version),   source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote} {{ ... p4 client -o jenkins-master - {color:#14892c}scm-promote{color}_ansible_playbooks-0 + }}  {{  ... p4 client -i + }}  {{  P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. }}  {{  Mapping '//jenkins-master-{color:#ff}scm/promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.  }} {quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message

[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin

2018-03-27 Thread mr...@sjm.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Rose updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50441  
 
 
  p4sync with default client name fails with latest version of p4 plugin   
 

  
 
 
 
 

 
Change By: 
 Michael Rose  
 

  
 
 
 
 

 
 This used to work:{quote}p4sync credential: 'p4integ.prod',   populate: previewOnly(quiet: true, pin: env.latest_version),   source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote}... p4 client o jenkins-master-{color:#14892c}scm * - * promote{color}_ansible_playbooks-0 + ... p4 client -i + P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Mapping '//jenkins-master-{color:#ff}scm * / * promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.{quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed

[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin

2018-03-27 Thread mr...@sjm.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Rose updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50441  
 
 
  p4sync with default client name fails with latest version of p4 plugin   
 

  
 
 
 
 

 
Change By: 
 Michael Rose  
 

  
 
 
 
 

 
 This used to work:{quote}p4sync credential: 'p4integ.prod',   populate: previewOnly(quiet: true, pin: env.latest_version),   source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote}... p4 client  -  o jenkins-master-{color:#14892c}scm-promote{color}_ansible_playbooks-0 + ... p4 client -i + P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Mapping '//jenkins-master-{color:#ff}scm/promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.{quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin

2018-03-27 Thread mr...@sjm.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Rose updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50441  
 
 
  p4sync with default client name fails with latest version of p4 plugin   
 

  
 
 
 
 

 
Change By: 
 Michael Rose  
 

  
 
 
 
 

 
 This used to work:{quote}p4sync credential: 'p4integ.prod',  populate: previewOnly(quiet: true, pin: env.latest_version),  source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote}... p4 client  - o jenkins-master-{color:#14892c}scm*-*promote{color}_ansible_playbooks-0 +... p4 client -i +P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.Mapping '//jenkins-master-{color:#ff}scm*/*promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.{quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin

2018-03-27 Thread mr...@sjm.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Rose created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50441  
 
 
  p4sync with default client name fails with latest version of p4 plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Paul Allen  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-03-27 22:12  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Rose  
 

  
 
 
 
 

 
 This used to work: 

p4sync credential: 'p4integ.prod',   populate: previewOnly(quiet: true, pin: env.latest_version),   source: depotSource('//foo/bar/playbooks')
 Now it produces the following error message: 

... p4 client o jenkins-masterscm*-*promote_ansible_playbooks-0 + ... p4 client -i + P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Mapping '//jenkins-master-scm*/*promote_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.
 Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.