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

2016-11-15 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in 1.4.9  
 

  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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-11-10 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated  JENKINS-38425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Ready for release  
 

  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-11-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: call to p4 trigger blocked / waits until current job completes   
 

  
 
 
 
 

 
 Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java http://jenkins-ci.org/commit/p4-plugin/48ddd3bbe8b96b9b7f0172345f9c2f008fbe1987 Log: Allow concurrent use a Client during polling. Prevents Jenkins from blocking trigger events when polling and a build is in progress. JENKINS-38425  
 

  
 
 
 
 

 
 
 

 
 
 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-11-10 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-38425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: call to p4 trigger blocked / waits until current job completes   
 

  
 
 
 
 

 
 Turns out it is the polling part of the trigger event is blocking and not the build queue. If the workspace is in use for a build, it will block later polling attempts. Easy options: 1. detect build is in progress and reject/ignore the trigger event. 2. detect build is in progress and add to build queue without using polling to check for a change. Harder options: 3. use a special polling workspace 4. prevent polling from blocking  
 

  
 
 
 
 

 
 
 

 
 
 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-11-10 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated  JENKINS-38425  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-11-09 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth commented on  JENKINS-38425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: call to p4 trigger blocked / waits until current job completes   
 

  
 
 
 
 

 
 Clarification - If job is triggered and long running, this blocks further calls to the trigger URL until the job completes.  
 

  
 
 
 
 

 
 
 

 
 
 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-11-09 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth started work on  JENKINS-38425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-11-09 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth assigned an issue to Karl Wirth  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Assignee: 
 Karl Wirth  
 

  
 
 
 
 

 
 
 

 
 
 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