[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-31259) Checking remote job needs delay

2016-01-05 Thread hilton.campb...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hilton Campbell commented on  JENKINS-31259 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Checking remote job needs delay  
 
 
 
 
 
 
 
 
 
 
We're experiencing the same problem. It's pretty severe all of a sudden, I don't know why. Maybe I've only just started noticing it. I tried the workaround but it doesn't seem to help. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [parameterized-remote-trigger-plugin] (JENKINS-31259) Checking remote job needs delay

2015-10-29 Thread m...@florian-hopf.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Florian Hopf created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31259 
 
 
 
  Checking remote job needs delay  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Maurice W. 
 
 
 

Components:
 

 parameterized-remote-trigger-plugin 
 
 
 

Created:
 

 29/Oct/15 2:28 PM 
 
 
 

Labels:
 

 plugins 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Florian Hopf 
 
 
 
 
 
 
 
 
 
 
When triggering a remote build the plugin tries to determine the next job number in advance. After calling start on the remote job It then checks if the job is started.  
In our case the first call to our job returns an empty response, probably because it takes too long to initialize. The plugin then tries to iterate older jobs and probably even finds one that has the same paramters. This can then lead to not waiting for the job to be build. 
In our case this is critical because we are starting several remote jobs that need to be run sequentially. So the next job gets startet too early and both jobs are run in parallel when they should be executed sequentially.  
Workaround: Add a timestamp parameter to the build so that all execution parameter sets are unique. 
Pull request with a better fix coming soon., 
 
 
 
   

[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-31259) Checking remote job needs delay

2015-10-29 Thread m...@florian-hopf.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Florian Hopf commented on  JENKINS-31259 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Checking remote job needs delay  
 
 
 
 
 
 
 
 
 
 
Pull request is at https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/17 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.