[JIRA] (JENKINS-58936) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jell
Title: Message Title Darrien Glasser commented on JENKINS-58936 Re: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jelly:46:53: We're also on jenkins 2.190-1 and hitting the same error. The Manage Jenkins page hits the stacktrace every time without fail, so we can't do any administration. There's a new version so we can try and upgrade to that, but at the moment, this is very frustrating. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201280.1565796626000.2940.1567108320135%40Atlassian.JIRA.
[JIRA] (JENKINS-58863) Builds cannot start after upgrading
Title: Message Title Darrien Glasser edited a comment on JENKINS-58863 Re: Builds cannot start after upgrading All of my builds have started failing after about 5 minutes with the same error. This also happened around the same time as the upgrade. Edit: Confirming that rolling back to 1.17.1 fixes the issues we were having. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201178.1565282292000.8715.1566567420243%40Atlassian.JIRA.
[JIRA] (JENKINS-58863) Builds cannot start after upgrading
Title: Message Title Darrien Glasser commented on JENKINS-58863 Re: Builds cannot start after upgrading All of my builds have started failing after about 5 minutes with the same error. This also happened around the same time as the upgrade. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201178.1565282292000.8158.1566499740244%40Atlassian.JIRA.
[JIRA] (JENKINS-52636) Gerrit triggered jobs getting delayed
Title: Message Title Darrien Glasser commented on JENKINS-52636 Re: Gerrit triggered jobs getting delayed It doesn't look like there's been any action on the PR yet although it mostly looks good to go from here. In the meantime, I have a patched version we're using at the company I'm at. You're free to use while we wait: https://github.com/DarrienG/gerrit-trigger-plugin/releases/tag/2.31.0-uninterested It's basically HEAD from the official repo + ignores irrelevant events. We have probably 3000+ builds a day and haven't seen any issues with it while we wait. Jenkins was unusable for us otherwise. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.192488.1531933057000.2215.1564254180518%40Atlassian.JIRA.
[JIRA] (JENKINS-57184) Kubernetes Plugin inversely applies NodeSelector
Title: Message Title Darrien Glasser created an issue Jenkins / JENKINS-57184 Kubernetes Plugin inversely applies NodeSelector Issue Type: Bug Assignee: Carlos Sanchez Attachments: Screen Shot 2019-04-25 at 9.20.37 AM.png Components: kubernetes-plugin Created: 2019-04-25 14:16 Environment: Jenkins version 2.173 Host OS: CentOS 7 openjdk version "1.8.0_181" Kubernetes Plugin version: 1.15.1 Kubernetes version: 1.13.2 Kubernetes nodes: Container Linux by CoreOS 1911.4.0 (Rhyolite) Priority: Minor Reporter: Darrien Glasser Adding a NodeSelector to slaves provisioned with the Kubernetes appears to apply an anti-affinity to that NodeSelector rather than actually using the NodeSelector. We share our Kubernetes Cluster with Jenkins and a number of other projects. For our Jenkins slaves, we only want certain fast nodes, so they're labeled with `jenkins-slave=true` and our slow nodes do not have that corresponding label. When configuring slaves in Jenkins, we applied the NodeSelector with the given label: With the expectation it would only run on the fast nodes. But instead it only ran on the slow nodes without the label. It seems like rather than apply a NodeSelector, it's applying the opposite of the NodeSelector (anti-affinity). We can't do too much testing on our production instance of Jenkins, so for now we've just removed the NodeSelector and are letting Jenkins Slaves run everywhere, but this is very frustrating when a slave is scheduled on our slow nodes.
[JIRA] (JENKINS-31430) Gerrit Trigger Plugin: shouldn't mark aborted jobs as failure
Title: Message Title Darrien Glasser commented on JENKINS-31430 Re: Gerrit Trigger Plugin: shouldn't mark aborted jobs as failure This is still an issue. We ran into this today. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52636) Gerrit triggered jobs getting delayed
Title: Message Title Darrien Glasser edited a comment on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Our team has confirmed that Gerrit trigger listens to all gerrit events, including ones it cannot act upon. It takes an inordinate time to determine whether or not it is able to act on them, finally only throwing a `NoSuchMethodException` trying to reflect into an object and see if the event has what it is looking for.This wasn't really an issue before, as all data was stored in SQL somewhere. NoteDB stores all data (events included) in refs/changes/* which all generate events that Jenkins listens for.We started using the replication plugin, and added reviewers automatically when a review was posted, and our Jenkins server was inundated almost immediately.As it stands, this makes the gerrit-trigger plugin unusable for anybody using the replication plugin, and as gerrit generates more metadata over time, will make the plugin unusable in all general cases unless it starts only listening to relevant events. We've found this gerrit trigger implemented with pipelines does not have the issue [https://github.com/jenkinsci/gerrit-code-review-plugin]And will likely be switching to it in the future. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52636) Gerrit triggered jobs getting delayed
Title: Message Title Darrien Glasser commented on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Our team has confirmed that Gerrit trigger listens to all gerrit events, including ones it cannot act upon. It takes an inordinate time to determine whether or not it is able to act on them, finally only throwing a `NoSuchMethodException` trying to reflect into an object and see if the event has what it is looking for. This wasn't really an issue before, as all data was stored in SQL somewhere. NoteDB stores all data (events included) in refs/changes/* which all generate events that Jenkins listens for. We started using the replication plugin, and added reviewers automatically when a review was posted, and our Jenkins server was inundated almost immediately. As it stands, this makes the gerrit-trigger plugin unusable for anybody using the replication plugin, and as gerrit generates more metadata over time, will make the plugin unusable in all general cases unless it starts only listening to relevant events. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52636) Gerrit triggered jobs getting delayed
Title: Message Title Darrien Glasser edited a comment on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Update, we've been debugging this issue, and it seems like the Replication Plugin may be (somehow) interfering with the missed events playback plugin/event trigger.We're not entirely certain, but it almost looks like the event trigger (that sends builds to Jenkins) is receiving replication events and gets stuck trying to understand what to do with them.We will continue investigating. Disabling the replication plugin reduces our backlog queue to 0 and events are perfectly streamed to Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52636) Gerrit triggered jobs getting delayed
Title: Message Title Darrien Glasser commented on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Update, we've been debugging this issue, and it seems like the Replication Plugin may be (somehow) interfering with the missed events playback plugin/event trigger. We're not entirely certain, but it almost looks like the event trigger (that sends builds to Jenkins) is receiving replication events and gets stuck trying to understand what to do with them. We will continue investigating. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52636) Gerrit triggered jobs getting delayed
Title: Message Title Darrien Glasser commented on JENKINS-52636 Re: Gerrit triggered jobs getting delayed We're having the same issue. Running on a machine with 32 cores we have a ton of events queued up and the trigger is barely able to keep up with them. Sometimes Jenkins appears to be dropping builds because of this and some of the requests are not honored. Our updated thread pool size doesn't appear to be taking effect (although that should be put in a different issues). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
