[JIRA] [core] (JENKINS-17667) Unable to kill a job which is running
Steven Deal commented on JENKINS-17667 Unable to kill a job which is running I've seen this from time to time. Any attempt at killing the job is useless (from the gui, from a curl command). I have seen this more frequently in the past and now it's back. I'm suspecting it may be related to using locks and latches... I wonder if there's a timeout that may have been exceeded and it's left in a state of limbo. 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] [core] (JENKINS-17667) Unable to kill a job which is running
Steven Deal edited a comment on JENKINS-17667 Unable to kill a job which is running I've seen this from time to time. Any attempt at killing the job is useless (from the gui, from a curl command). I have seen this more frequently in the past and now it's back. I'm suspecting it may be related to using locks and latches... I wonder if there's a timeout that may have been exceeded and it's left in a state of limbo. One thing I can suggest... it's rather drastic. But as I'm a pretty heavy user of the jenkins cli, if you pull down the job configuration, you can delete the job (removing this ghost running build) and recreate the job. You loose build history etc. but if you really need to get rid of it and a restart of Jenkins is simply out of the question. jenkins get-job abc config.xml jenkins delete-job abc jenkins create-job abc config.xml hth,steven and of course 'jenkins' in the above example is a shell script of #!/bin/bash java -jar ~/bin/jenkins-cli.jar -s https://jenkins_url -i ~/.ssh/id_rsa $@ 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] [core] (JENKINS-17667) Unable to kill a job which is running
Steven Deal edited a comment on JENKINS-17667 Unable to kill a job which is running I've seen this from time to time. Any attempt at killing the job is useless (from the gui, from a curl command). I have seen this more frequently in the past and now it's back. I'm suspecting it may be related to using locks and latches... I wonder if there's a timeout that may have been exceeded and it's left in a state of limbo. One thing I can suggest... it's rather drastic. But as I'm a pretty heavy user of the jenkins cli, if you pull down the job configuration, you can delete the job (removing this ghost running build) and recreate the job. You loose build history etc. but if you really need to get rid of it and a restart of Jenkins is simply out of the question. jenkins get-job abc config.xml jenkins delete-job abc jenkins create-job abc config.xml hth,steven and of course 'jenkins' in the above example is a shell script of #!/bin/bash java -jar ~/bin/jenkins-cli.jar -s https://jenkins_url -i ~/.ssh/id_rsa $@ And by the way... having used commercial software for years.. I've never seen the level of response that's being suggested. 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] [build-pipeline] (JENKINS-17939) Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist.
Steven Deal commented on JENKINS-17939 Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesnt exist. I experienced this as well, both with the current code base as well as going back to the 1.3.3 time frame with 34c17d66dc3fae5cdd52efb387e4ae1e97a040d2. However, I found that if I removed the old plugin folder and the build-pipeline-plugin.jpi file, copied the new build-pipeline-plugin.hpi to the plugins folder, renamed as a jpi file. It deployed successfully. I don't know which of these steps were the 'fix'. 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-17939) Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist.
Steven Deal edited a comment on JENKINS-17939 Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesnt exist. I experienced this as well, both with the current code base as well as going back to the 1.3.3 time frame with 34c17d66dc3fae5cdd52efb387e4ae1e97a040d2. However, I found that if I removed the old plugin folder and the build-pipeline-plugin.jpi file, copied the new build-pipeline-plugin.hpi to the plugins folder, renamed as a jpi file. It deployed successfully. I don't know which of these steps were the 'fix'. Actually, this did not work for the current head. 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/groups/opt_out.
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Steven Deal commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I manually reverted back to email-ext 2.28 and after 12+ hours of uptime, not only has this problem gone away (and not returned), another issue I was having where clicking 'configure' on any job would peg the cpu at 100% has gone away as well. Per the previous post, maybe there is something wrong with the install process outside of this plugin as I 'downgraded' through the web interface to 2.28 and found that I was still running 2.29 w/ the problem. I'd love to manually install 2.29 but having suffered with 2+ weeks of critical jenkins problems we need some stability here. 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/groups/opt_out.
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Steven Deal commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I'm not familiar with groovy; but, why would this work immediately after a restart and then break at a later time? 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/groups/opt_out.
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Steven Deal commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I use Email Ext and did upgrade to 2.29. I cannot say with confidence if this issue started with that upgrade. I noticed email-ext in a thread dump of another issue I'm currently having and did try to downgrade. However, I just noticed that my jenkins instance still appears to be running 2.29 and I no longer have the 'downgrade' option on the plugins screen. Guess I'll have to search around for the older email-ext.jpi. I'll certainly update this thread if a down grade resolves 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/groups/opt_out.
