[JIRA] [parameterized-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted

2014-09-17 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 updated  JENKINS-24731


Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
















Not a core issue. There's little core can do about a plugin that catches InterruptedException in what's effectively a 'while(true)' loop.





Change By:


Daniel Beck
(17/Sep/14 7:30 AM)




Component/s:


core



























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] [parameterized-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted

2014-09-17 Thread lorelei.mccol...@gmail.com (JIRA)














































Lorelei McCollum
 commented on  JENKINS-24731


Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted















Ahh Thanks for the information, I didn't know if core would allow things like this or not. Not good though. Hopefully the plugin team can get a fix out for this



























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] [parameterized-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted

2014-09-17 Thread lorelei.mccol...@gmail.com (JIRA)














































Lorelei McCollum
 commented on  JENKINS-24731


Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted















This is the issue in the code

 while (preCheckResponse.getBoolean("building") == true || preCheckResponse.getString("result") == null) {
listener.getLogger().println("Remote build is currently running - waiting for it to finish.");
preCheckResponse = sendHTTPCall(preCheckUrlString, "POST", build, listener);
listener.getLogger().println("Waiting for " + this.pollInterval + " seconds until next retry.");
// Sleep for 'pollInterval' seconds.
// Sleep takes miliseconds so need to convert this.pollInterval to milisecopnds (x 1000)
try {
Thread.sleep(this.pollInterval * 1000);
} catch (InterruptedException e) {
this.failBuild(e, listener);
}
}


failBuild never is allowed to get into the abort exception because the boolean variable that would allow that is never modified after instance created



























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] [parameterized-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted

2014-09-16 Thread lorelei.mccol...@gmail.com (JIRA)














































Lorelei McCollum
 created  JENKINS-24731


Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted















Issue Type:


Bug



Assignee:


Maurice W.



Components:


parameterized-remote-trigger



Created:


16/Sep/14 10:46 PM



Description:


Using this to execute a remote job on another jenkins system
I had the block check box checked and was trying to use a properties file in the workspace for the parameters

The job never triggered the remote job on the other jenkins server. The other jenkins server is indeed up. Predefined params with same configuration was working. When tried to do this with properties file check box.. the job got into a BAD state. I tried to abort, did not work. I tried to toggle node offline and disconnect the node, did not work

The job is in an infinite loop this is REALLY bad
I cannot kill this job. I think I am going to kill the process on the node.


EnvInject - Loading node environment variables.
Building remotely on rh632-us506 in workspace /var/lib/jenkins/workspace/LLBB3-Work-Queue
Run condition Regular _expression_ match enabling prebuild for step Trigger/call builds on other projects
Run condition Regular _expression_ match enabling prebuild for step Trigger a remote parameterized job
LLBB3-Work-Queue $ /bin/sh -xe /tmp/hudson3940059047949035559.sh
+ echo 3133
3133
+ echo SequoiaBuild=3133
Regular _expression_ run condition: _expression_=^SCN$, Label=Sequoia
Run condition Regular _expression_ match preventing perform for step Trigger/call builds on other projects
Regular _expression_ run condition: _expression_=^Sequoia$, Label=Sequoia
Run condition Regular _expression_ match enabling perform for step Trigger a remote parameterized job
Triggering this remote job: BVT1-csdl-glider-1
Not checking if the remote job BVT1-csdl-glider-1 is building.
This job is build #111 on the remote server.
Triggering remote job now.
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #1 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #2 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #3 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #4 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #5 out of 5
ERROR: Remote build failed for the following reason, but the build will continue:
ERROR: Max number of connection retries have been exeeded.
Blocking local job until remote job completes
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #1 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #2 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #3 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #4 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #5 out of 5
ERROR: Remote build failed for the following reason, but the build will continue:
ERROR: Max number of connection retries have been exeeded.
Waiting for remote build to start.
Waiting for 60 seconds until next poll.
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #1 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #2 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #3 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #4 out of 5
Connection to remote server failed, waiting for to retry - 60 seconds until next attempt.
Retry attempt #5 out of 5
ERROR: Remote build failed for the