[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Peter Krefting commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade Downgrading to http://mirrors.jenkins-ci.org/debian/jenkins_2.205_all.deb the build queue is still stuck. Downgrading to http://pkg.jenkins-ci.org/debian-stable/binary/jenkins_2.204.6_all.deb the builds start running again. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205618.158582599.6863.1586171400188%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Peter Krefting commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade Is there a 2.205 DEB that I can install to see if it has the same behaviour (if the configuration is downward compatible)? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205618.158582599.6696.1586153640116%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Peter Krefting updated an issue Jenkins / JENKINS-61779 Regression: Job stuck in queue waiting forever after upgrade Change By: Peter Krefting Summary: Regression: Job stock stuck in queue waiting forever after upgrade Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205618.158582599.5181.1585831800075%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stock in queue waiting forever after upgrade
Title: Message Title Peter Krefting created an issue Jenkins / JENKINS-61779 Regression: Job stock in queue waiting forever after upgrade Issue Type: Bug Assignee: Unassigned Attachments: waiting.png Components: core, throttle-concurrent-builds-plugin Created: 2020-04-02 11:13 Environment: Jenkins 2.222.1 throttle-concurrents 2.0.2 Debian GNU/Linux 10.3 amd64 Java 11.0.6+10-post-Debian-1deb10u1 Labels: regression throttle Priority: Minor Reporter: Peter Krefting I "apt dist-upgrade"-d my build Jenkins server, and was updated from 2.204.4 to 2.222.1, and now I am running into issues. The major issue is that my throttled builds do not work. I have a build (see attached creenshot) that is configured with throttling: 1 1 vm-installer kickstart-repo true category true false true 1 It is set up to build on a single node: label kickstartbuild The pop-up says that is waiting for the next available executor, which is "master", which is the only one satisfying this label. It is idle, but Jenkins is still waiting. The configuration worked fine before upgrading. Restarting Jenkins does not help.
[JIRA] [git-plugin] (JENKINS-32029) "Oops!" when trying to change project configuration
Title: Message Title
Peter Krefting created an issue
Jenkins / JENKINS-32029
"Oops!" when trying to change project configuration
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
11/Dec/15 12:46 PM
Environment:
Jenkins 1.641 on Debian GNU/Linux 8.2 amd64, .deb install. and Jenkins 1.641 on CentOS 7.1 amd64, .rpm install.
Priority:
Minor
Reporter:
Peter Krefting
After a recent update I can no longer change configuration of any Jenkins project on either of my two installs (one DEB and RPM). When I press Save, I get an "Oops!" with the following stack trace, which seems to indicate an infinite recursion going on:
{{javax.servlet.ServletException: java.lang.StackOverflowError at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.Se
