[JIRA] (JENKINS-55020) poll using build parameters

2018-12-04 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55020  
 
 
  poll using build parameters   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-12-05 00:42  
 
 
Labels: 
 P4_VERIFY  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 When polling, expand the build parameters. Have hidden build parameter(hidden parameters plugin ) called BRANCH.   Thus this can be treated as a constant. I'd like to use ${BRANCH} in the client name for the polling, but the value of BRANCH is not made available.   (It is there for the build job) Use case: Overall goal would be to be able to create build jobs quickly when a new branch is created. Ideally, I just want to be able to create a new job by copying and simply change one or two variables - the branch and the build version number.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-54762) Show output from reconcile -w -f step of Auto Cleanup and Sync

2018-11-21 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54762  
 
 
  Show output from reconcile -w -f step of Auto Cleanup and Sync   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 

  
 
 
 
 

 
 If "QUIET Perforce messages" is unchecked, the job's console log should show the output from the "p4 reconcile -w -f" in the populate option Auto Cleanup and Sync. Even a simple:    like:   /jenkins/job/abc/workspace/path/to/modifed refreshed   /jenkins/job/abc/workspace/path/to/newFile deleted  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54762) Show output from reconcile -w -f step of Auto Cleanup and Sync

2018-11-21 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54762  
 
 
  Show output from reconcile -w -f step of Auto Cleanup and Sync   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 
 
Labels: 
 P4_VERIFY  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54762) Show output from reconcile -w -f step of Auto Cleanup and Sync

2018-11-21 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54762  
 
 
  Show output from reconcile -w -f step of Auto Cleanup and Sync   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-11-21 23:49  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 If "QUIET Perforce messages" is unchecked, the job's console log should show the output from the "p4 reconcile -w -f" in the populate option Auto Cleanup and Sync.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira

[JIRA] (JENKINS-54707) Allow setting of P4IGNORE to alternate names

2018-11-19 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54707  
 
 
  Allow setting of P4IGNORE to alternate names   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-11-20 00:14  
 
 
Labels: 
 P4_VERIFY  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 Need a way to specify an alternative for P4IGNORE and/or not use it. setIgnoreFileName() is always set in https://swarm.workshop.perforce.com/projects/p4-jenkins/files/main/src/main/java/org/jenkinsci/plugins/p4/client/ConnectionHelper.java    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-50298) Use p4trust file if credential's Trust fingerprint is blank

2018-11-15 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50298  
 
 
  Use p4trust file if credential's Trust fingerprint is blank   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 

  
 
 
 
 

 
 If the credential's Trust field is blank,  just  use the fingerprint from the p4trust file.This means any node using this credential must have a P4TRUST file that already trusts the server.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-50298) Use p4trust file if credential's Trust fingerprint is blank

2018-11-15 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50298  
 
 
  Use p4trust file if credential's Trust fingerprint is blank   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 
 
Labels: 
 P4_SUPPORT P4_VERIFY  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-50298) Use p4trust file if credential's Trust fingerprint is blank

2018-11-13 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50298  
 
 
  Use p4trust file if credential's Trust fingerprint is blank   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 
 
Labels: 
 P4_SUPPORT  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-32791) overlay mappings when using polling can cause a build every poll

2018-09-27 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Does not reproduce in 1.8.15.   Closing.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-32791  
 
 
  overlay mappings when using polling can cause a build every poll   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-52861) p4sync's depotSource doesn't handle exclusionary mappings

2018-08-02 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52861  
 
 
  p4sync's depotSource doesn't handle exclusionary mappings   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 

  
 
 
 
 

 
  See client/ViewMapHelper.getClientView() - there's no check for a leading "-".Workaround:  use a template workspace.Repro:   make a p4sync with "Depot Sources" with one good line and one exclusionary path//depot/cases/...-//depot/cases/diff2/.. . p4sync then has:source: depotSource('''//depot/cases/...-//depot/cases/diff2/...''')Console log errro is:P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.Error detected at line 17.Null directory (//) not allowed in '///depot/cases/diff2/...'.Null directory (//) not allowed in '///depot/cases/diff2/...'.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-52861) p4sync's depotSource doesn't handle exclusionary mappings

2018-08-02 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52861  
 
 
  p4sync's depotSource doesn't handle exclusionary mappings   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-08-02 18:29  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
   See client/ViewMapHelper.getClientView() - there's no check for a leading "-". Workaround:  use a template workspace. Repro:   make a p4sync with "Depot Sources" with one good line and one exclusionary path //depot/cases/... -//depot/cases/diff2/.. p4sync then has: source: depotSource('''//depot/cases/... -//depot/cases/diff2/...''') Console log errro is: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Error detected at line 17. Null directory (//) not allowed in '///depot/cases/diff2/...'. Null directory (//) not allowed in '///depot/cases/diff2/...'.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-49804) Multibranch Helix Branches: support exclusionary mapping?

2018-08-01 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown commented on  JENKINS-49804  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Helix Branches: support exclusionary mapping?   
 

  
 
 
 
 

 
 Important recommendations is now at https://github.com/jenkinsci/p4-plugin/blob/master/docs/WORKFLOW.md#important-recommendations-1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-50298) Use p4trust file if credential's Trust fingerprint is blank

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


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50298  
 
 
  Use p4trust file if credential's Trust fingerprint is blank   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-03-20 17:22  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 If the credential's Trust field is blank, use the fingerprint from the p4trust file. This means any node using this credential must have a P4TRUST file that already trusts the server.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA

[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-38233) Enable review builds with pipeline scripts

2017-03-22 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 reopening since broken in 1.5.1  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38233  
 
 
  Enable review builds with pipeline scripts   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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-38233) Enable review builds with pipeline scripts

2017-03-22 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown commented on  JENKINS-38233  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Enable review builds with pipeline scripts   
 

  
 
 
 
 

 
 Broken in 1.5.1, worked in 1.4.9 Repro:  in browser, navigate to pipeline job (http://jenkinsHost/job/PIPELINE-JOB) and append /review/build to the address. actual:  404 not found expected:  build triggered   Swarm log: 2017-03-22T15:42:44-07:00 ERR (3): Failed to trigger automated tests: http://jbrown-p4.das.perforce.com:8080/job/piper/review/build?status=shelved=751=753=http%3 A%2F%2Fjbrown-swarm.das.perforce.com%2Freviews%2F751%2Ftests%2Fpass%2F7A3CA388-112E-42DE-F37A-9237B49285D0.v2%2F=http%3A%2F%2Fjbrown-swarm.das.perforce.com%2Freviews%2F751%2Ft ests%2Ffail%2F7A3CA388-112E-42DE-F37A-9237B49285D0.v2%2F (404 - ).  
 

  
 
 
 
 

 
 
 

 
 
 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-34825) Jobs in Folders should show credentials bound in the credential domain

2017-02-15 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown commented on  JENKINS-34825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jobs in Folders should show credentials bound in the credential domain   
 

  
 
 
 
 

 
 This is a security requirement. Folders can be limited to certain users, meaning only those users can use and see that folder's credentials.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-42029) Add "pin build at label" to Preview Check Only populate options

2017-02-14 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42029  
 
 
  Add "pin build at label" to Preview Check Only populate options   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2017/Feb/14 6:58 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 When choosing the Preview Check Only populate option allow for setting of the "Pin build at Perforce Label". Right now Pinning is available on the other options, just not the Preview Check.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by

[JIRA] (JENKINS-40292) More Control of p4 task logging

2016-12-07 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40292  
 
 
  More Control of p4 task logging
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2016/Dec/07 8:04 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 Desire a way to control (limit) the logging in the Console Output.  For example, when things go wrong in the actual build step, I always have to scroll done through all the P4 Tasks. There's part of the P4 Task output, like p4 info, p4 counter change, p4 client -i, p4 client -o, etc. that I only care about if it fails.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-40292) More Control of p4 task logging

2016-12-07 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40292  
 
 
  More Control of p4 task logging
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 
 
Issue Type: 
 Bug Improvement  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38425) call to p4 trigger blocked / waits until current job completes

2016-09-21 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38425  
 
 
  call to p4 trigger blocked / waits until current job completes   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 

  
 
 
 
 

 
 An http call to trigger a build using http://host/p4/change will hang when a build is already running.Expected:  returns immediately, build scheduledActual:  waits until current job finished, build scheduledThis means you should not syncronously call curl within a perforce change-commit trigger as it will delay completion of the submit.   Instead, you should asynchronously make the /p4/change call as other network issues, not just this issue, can also delay the response. Repro:add a build step to 'sleep 100'.   Start a build.  Now issue the curl call to /p4/change.  You'll see curl doesn't finish until the build finished.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38425) call to p4 trigger blocked / waits until current job completes

2016-09-21 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38425  
 
 
  call to p4 trigger blocked / waits until current job completes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2016/Sep/21 4:19 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 An http call to trigger a build using http://host/p4/change will hang when a build is already running. Expected: returns immediately, build scheduled Actual: waits until current job finished, build scheduled This means you should not syncronously call curl within a perforce change-commit trigger as it will delay completion of the submit. Instead, you should asynchronously make the /p4/change call as other network issues, not just this issue, can also delay the response.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-34037) P4 polling always triggers if matrix axis is built on a different slave

2016-09-08 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown commented on  JENKINS-34037  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: P4 polling always triggers if matrix axis is built on a different slave   
 

  
 
 
 
 

 
 Actually, I see polling always triggering a build for a matrix job with a build axis: After the first poll we see these 5 clients (job name is matrix) Client jenkins-jbrown-centos7-matrix-label-jbrown-centos7 2016/09/08 root /jenkins-slave/workspace/matrix/label/jbrown-centos7 'Change:592 ' Client jenkins-jbrown-p4-u15.das.perforce.com-matrix-label-jbrown-p4-u15.das.perforce.com 2016/09/08 root /jenkins-slave/workspace/matrix/label/jbrown-p4-u15.das.perf orce.com 'Change:592 ' Client jenkins-master-matrix 2016/09/08 root /var/lib/jenkins/jobs/matrix/workspace '' Client jenkins-master-matrix-label-jbrown-centos7 2016/09/08 root null '' Client jenkins-master-matrix-label-jbrown-p4-u15.das.perforce.com 2016/09/08 root null '' I added "Description: Change 592" to the 3 jenkins-master-matrix* clients, it will then build.  After the next build: Client jenkins-jbrown-centos7-matrix-label-jbrown-centos7 2016/09/08 root /jenkins-slave/workspace/matrix/label/jbrown-centos7 'Change:593 ' Client jenkins-jbrown-p4-u15.das.perforce.com-matrix-label-jbrown-p4-u15.das.perforce.com 2016/09/08 root /jenkins-slave/workspace/matrix/label/jbrown-p4-u15.das.perf orce.com 'Change:593 ' Client jenkins-master-matrix 2016/09/08 root /var/lib/jenkins/jobs/matrix/workspace 'Change: 592 ' Client jenkins-master-matrix-label-jbrown-centos7 2016/09/08 root null 'Change: 592 ' Client jenkins-master-matrix-label-jbrown-p4-u15.das.perforce.com 2016/09/08 root null 'Change: 592 ' The jenkins-master-matrix* clients are used for polling - that description didn't change so it builds again. My setup: Create a stream depot with depth=2 put some files into the stream – e.g., //stream2/simple-ant/main Create two additional slave nodes (all master/slaves all unix) Create matrix (Mulit-configuration) project (I called in matrix). Check disable this project for now. 
 
Take defaults for SCM (workspace name of jenkins-$ {NODE_NAME} -$ {JOB_NAME} , Auto cleanup and sync, uncheck quiet) 
 Build triger: Poll SCM (I used H/5 * * * *) Add axis: slaves. Check your two nodes (master not checked)  I let polling trigger the first build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-38076) p4-plugin: p4d log file has strange program/version for plugin's commands

2016-09-08 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38076  
 
 
  p4-plugin: p4d log file has strange program/version for plugin's commands   
 

  
 
 
 
 

 
Change By: 
 Joel Brown  
 

  
 
 
 
 

 
 Sample: {{ Perforce server info:2016/09/08 14:48:08 pid 45912 build@_CLIENT_UNSET_ 10.5.10.202 [jenkins.${project.artifactId}-plugin/${project.version}/Linux] 'user-client -o  j  ...}}   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38076) p4-plugin: p4d log file has strange program/version for plugin's commands

2016-09-08 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38076  
 
 
  p4-plugin: p4d log file has strange program/version for plugin's commands   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2016/Sep/08 10:09 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 Sample: Perforce server info: 2016/09/08 14:48:08 pid 45912 build@CLIENT_UNSET 10.5.10.202 [jenkins.$ {project.artifactId} -plugin/$ {project.version} /Linux] 'user-client -o j  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by

[JIRA] (JENKINS-37124) First build syncs to lowest change rather than highest

2016-08-02 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37124  
 
 
  First build syncs to lowest change rather than highest   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Paul Allen  
 
 
Attachments: 
 logs-and-config.zip  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2016/Aug/02 4:22 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 On first poll a build is triggered, but the build is done after syncing to the lowest changelist rather than the last/highest changelist. This happens when the plugin was upgraded from 1.3.x to 1.4.1. Logs attached. Workaround should be to disable polling, then "build now", then re-enable polling.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-37074) Implement ILogCallback

2016-07-29 Thread jbr...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37074  
 
 
  Implement ILogCallback   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2016/Jul/29 10:25 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Joel Brown  
 

  
 
 
 
 

 
 Sometimes P4Java does a log.error() and continues, in some cases causing problems down the road. If ILogCallback was setup we'd at least have a clue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[JIRA] [p4-plugin] (JENKINS-34825) Jobs in Folders should show credentials bound in the credential domain

2016-05-13 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34825 
 
 
 
  Jobs in Folders should show credentials bound in the credential domain  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 2016/May/13 11:00 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Joel Brown 
 
 
 
 
 
 
 
 
 
 
Credentials "bound" to the folder do not show in the credentials dropdown 
Repro: 
 

Install the Folders plugin
 

Create a Folder
 

Configure the Folder to have a Credential Domain, then a dd a Perforce Password credential to that domain
 

Create a job within the folder with SCM Perforce. View credentials from the dropdown
 
 
Expected: pick from global credentials and the credential just added in the folder's credential domain. 
Actual: only global credentials. 
I do have project team specific folders on the master and each has a local credential store

[JIRA] [p4-plugin] (JENKINS-34541) correct typo: Trust missmatch! Server fingerprint:

2016-05-02 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34541 
 
 
 
  correct typo: Trust missmatch! Server fingerprint:  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 2016/May/02 7:13 PM 
 
 
 

Priority:
 
  Trivial 
 
 
 

Reporter:
 
 Joel Brown 
 
 
 
 
 
 
 
 
 
 
From "missmatch" to "mismatch". two occurrences in: //guest/perforce_software/p4jenkins/main/src/main/java/org/jenkinsci/plugins/p4/client/ConnectionFactory.java 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [p4-plugin] (JENKINS-32791) overlay mappings when using polling can cause a build every poll

2016-02-04 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32791 
 
 
 
  overlay mappings when using polling can cause a build every poll  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 05/Feb/16 1:11 AM 
 
 
 

Environment:
 

 p4 plugin 1.3.6, jenkins 1.623, linux 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Joel Brown 
 
 
 
 
 
 
 
 
 
 
Create a manual client with an overlay mapping. Submit a file to the first mapping.  
The poll detects a change and builds. (This new version is always overlayed with the second mapping, so the build is no different that the last.) 
Next poll detects the same change and builds. 
Next poll detects the same change and builds. 
Forever. 
Repro example with files: 
I have //depot/main/simple-ant/... 
p4 integ //depot/main/simple-ant/... //depot/main/simple-ant - Copy/... 
View is //depot/main/simple-ant/... //client/... "+//depot/main/simple-any - Copy/..." //client/... 
Submit a new version in the first mapping ->

[JIRA] [p4-plugin] (JENKINS-31664) Help text for available Environment variable descriptions missing

2015-11-19 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31664 
 
 
 
  Help text for available Environment variable descriptions missing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 19/Nov/15 7:39 PM 
 
 
 

Priority:
 
  Trivial 
 
 
 

Reporter:
 
 Joel Brown 
 
 
 
 
 
 
 
 
 
 
The P4 env vars are described as P4 Plugin.blurb. 
Example: P4_PORT : P4 Plugin.blurb 
Click on a job -> Configure 
[scroll to ‘Build’ -> ‘Execute [ Windows Batch | Shell ] Command’]  
Under that box is a link to ‘See the list of available environment variables’ 
If you click that, you get help box/tab saying: 
--- The following variables are available to shell scripts [snip] 
JOB_URL Full URL of this job, like http://server:port/jenkins/job/foo/ (Jenkins URL must be set) 
P4_CHANGELIST P4 Plugin.blurb 
P4_CLIENT P4 Plugin.blurb 
P4_PORT P4 Plugin.blurb 
P4_USER P4 Plugin.blurb 
P4_TICKET 
P4 Plugin.blurb

[JIRA] [p4-plugin] (JENKINS-25364) Unable to update workspace error

2015-11-17 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown edited a comment on  JENKINS-25364 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to update workspace error  
 
 
 
 
 
 
 
 
 
 Regarding: com.perforce.p4java.exception.ConnectionException: For input string: "2235641344"You're trying to sync a file whose size is > java.lang.Integer.MAX_VALUEP4Java is trying to parse that string into an Integer.   This is a   P4Java bug:   job080413.  (Not yet fixed as of P4Java 2015.1) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-25364) Unable to update workspace error

2015-11-17 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown edited a comment on  JENKINS-25364 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to update workspace error  
 
 
 
 
 
 
 
 
 
 Regarding: com.perforce.p4java.exception.ConnectionException: For input string: "2235641344"You're trying to sync a file whose size is > java.lang.Integer.MAX_VALUEP4Java is trying to parse that string into an Integer.  P4Java bug:   job080413 .  (Not yet fixed as of P4Java 2015.1) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-25364) Unable to update workspace error

2015-11-17 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown commented on  JENKINS-25364 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to update workspace error  
 
 
 
 
 
 
 
 
 
 
Regarding: com.perforce.p4java.exception.ConnectionException: For input string: "2235641344" 
You're trying to sync a file whose size is > java.lang.Integer.MAX_VALUE 
P4Java is trying to parse that string into an Integer. P4Java bug: job080413 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-31306) rest api for view doesn't provide affectedPaths

2015-10-29 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown commented on  JENKINS-31306 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: rest api for view doesn't provide affectedPaths  
 
 
 
 
 
 
 
 
 
 
one simple solution is change P4ChangeEntry: 
{{ public Collection getAffectedPaths() { if ( affectedPaths.size() < 1 && files != null && files.size() > 0) { for (IFileSpec item : files)  { affectedPaths.add(item.getDepotPathString()); } 
 } return affectedPaths; }}} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-31306) rest api for view doesn't provide affectedPaths

2015-10-29 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31306 
 
 
 
  rest api for view doesn't provide affectedPaths  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 29/Oct/15 7:31 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Joel Brown 
 
 
 
 
 
 
 
 
 
 
rest call for a build does not populate the changeset's affectedPaths array. 
For example, a url like this: http://host:port/view/All/job/simple-ant/59/api/json 
To repro: pick a build with files and issue the rest url and note that the affectPaths is empty.  
If it's not empty restart jenkins to force a parse of JENKINS_HOME/jobs//builds//changelog.xml. 
The problem is that P4ChangeParser parses the changeentry's  element OK but does not set the P4ChangedEntry's affectedPaths from the files.  
 snipped of returned json with an empty affectedPaths: changeSet: { items: [ { affectedPaths: [ ], author:  { absoluteUrl: "http://jbrown-p4.das.perforce.com:8080/user/jbrown", fullName: "jbrown" } 
, commitId: null, msg: "dog", timestamp: -1, changeNumber: "126", changeTime: "2015-10-27 14:05:19" } ], kind: null },

[JIRA] [p4-plugin] (JENKINS-31306) rest api for view doesn't provide affectedPaths

2015-10-29 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown edited a comment on  JENKINS-31306 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: rest api for view doesn't provide affectedPaths  
 
 
 
 
 
 
 
 
 
 one simple solution is change P4ChangeEntry .java :{{   public Collection getAffectedPaths() { if ( affectedPaths.size() < 1 && files != null && files.size() > 0) { for (IFileSpec item : files) { affectedPaths.add(item.getDepotPathString()); } } return affectedPaths; }  }} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-29387) Cannot sync into workspaces with '@' in their path

2015-09-02 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown commented on  JENKINS-29387 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot sync into workspaces with '@' in their path  
 
 
 
 
 
 
 
 
 
 
Somewhat related: JENKINS-25242. Same issue with "@" in the path.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-25242) p4-plugin: Doesn't do concurrent builds

2015-09-01 Thread jbr...@perforce.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joel Brown commented on  JENKINS-25242 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: p4-plugin: Doesn't do concurrent builds  
 
 
 
 
 
 
 
 
 
 
The Perforce plugin substitutes %40 for the @ in the client root --> 
 Root: /var/lib/jenkins/jobs/sp4/workspace%402 
The 4 escaped chars in the local path are %,#, *, and @. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-27365) Perforce ticketed credentials in p4 plugin incompatible with p4 command-line behavior

2015-04-13 Thread jbr...@perforce.com (JIRA) 














































Joel Brown
 commented on  JENKINS-27365


Perforce ticketed credentials in p4 plugin incompatible with p4 command-line behavior















Can't repro, this works fine for me in 1.2.1:  I build using a ticket credential with a ticket value and no p4tickets file.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [p4-plugin] (JENKINS-27870) p4-plugin: Test Connection misleadingly fails for ticket cred when using ticket value

2015-04-13 Thread jbr...@perforce.com (JIRA) 














































Joel Brown
 commented on  JENKINS-27870


p4-plugin: Test Connection misleadingly fails for  ticket cred when using ticket value 















Fix is in 1.2.1.  Small note:  if you want to test your ticketPath, make sure the ticket value field is empty.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [p4-plugin] (JENKINS-27870) p4-plugin: Test Connection misleadingly fails for ticket cred when using ticket value

2015-04-13 Thread jbr...@perforce.com (JIRA) 















































Joel Brown
 closed  JENKINS-27870 as Fixed


p4-plugin: Test Connection misleadingly fails for  ticket cred when using ticket value 
















Change By:


Joel Brown
(13/Apr/15 11:39 PM)




Status:


Open
Closed





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [p4-plugin] (JENKINS-27870) p4-plugin: Test Connection misleadingly fails for ticket cred when using ticket value

2015-04-09 Thread jbr...@perforce.com (JIRA) 














































Joel Brown
 created  JENKINS-27870


p4-plugin: Test Connection misleadingly fails for  ticket cred when using ticket value 















Issue Type:


Bug



Assignee:


Unassigned


Components:


p4-plugin



Created:


09/Apr/15 5:50 PM



Description:


When creating a Perforce Ticket Credential, Using a Ticket Value, the "Test Connection" fails with a valid ticket entered.

Repro:
p4: obtain a valid ticket from the jenkins build machine to p4d.
Jenkins: Create a Perforce ticket credential.
select radio "use p4tickets file", enter bogus path of "/crap/out"
select radio "Login with ticket value" and enter a valid ticket
Click "Test connection"

Expected:  Success
Actual:  Authentication Error: Unable to login.

It's the "test connection" failure that is misleading  why would I build if the test fails?  Builds with this credential do work.  

I've tracked down the problem -- the Test Connection ajax request sends parameter "ticket: ticketPathSet" when it should have sent "ticket: ticketValueSet".




Project:


Jenkins



Priority:


Minor



Reporter:


Joel Brown

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [p4-plugin] (JENKINS-27250) p4 plugin does not respect line endings setting

2015-03-13 Thread jbr...@perforce.com (JIRA) 














































Joel Brown
 commented on  JENKINS-27250


p4 plugin does not respect line endings setting















The is a P4Java bug regarding files of perforce type UTF16+x (only UTF16 with a +x modifier)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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.