[JIRA] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Hi Mark, we currently prefer not to run via webhooks, because our tests (and deployments) take 20 minutes, and we get a few pushes per minute. In other words: we didn't want to overload our slaves (16 executors in total). We will re-evaluate a web-hook like system and also look into Gerrit and Zuul to limit the runtime. Thanks for your time. The ticket can be suspended. 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Hi Mark, Thank you for your answer. I understand your position. I'll see if I can get approval for using the freedomsponsors option. We also have an in-house Java team so maybe I can use them to debug this further. In the meantime I have another, related, question: I just noticed that there's a hudson.triggers.SCMTrigger.starvationThreshold "hidden" feature with its default set to 1 hour (description is "Milliseconds waiting for polling executor before trigger reports it is clogged"). We do a lot of polling, so would extending it to 2 hours or more potentially fix this? If that's the case, maybe it makes sense to use a separate polling thread in the Jenkins 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run What can I do to change that? It's kinda annoying when we're moving to continuous integration and only a handful of our jobs that poll work (and even then not as often as they should). 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Is there an update on this? We're upgrading our Jenkins-Job-Builder program soon. Some issues that were fixed had to do with polling. Even if they caused it, which isn't certain until we've tested it, I'd like to see a list of the "clogged" polls in Jenkins. 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run We're now at 1.609 . Our slaves are also updated to the latest slave.jar . Issue persists. Would like to be able to see if the polling thread is clogged up or not. 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run It works on some projects now, but it's still way below what we expect. Our main project with a lot of commits hasn't run since last Friday. Might be related to: https://issues.jenkins-ci.org/browse/JENKINS-26208 . I'll upgrade to 1.608. 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Just saw this in the log. This was in a merge request. We use the Gitlab Merge Request Builder plugin for that. Apr 07, 2015 3:59:42 PM hudson.triggers.Trigger checkTriggers WARNING: org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run() failed for hudson.model.FreeStyleProject@225cf060[myproject] java.lang.NullPointerException at org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run(GitlabBuildTrigger.java:100) at hudson.triggers.Trigger.checkTriggers(Trigger.java:265) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:214) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Is there a way to check the output of "isClogged()" in a log? Like https://github.com/jenkinsci/jenkins/blob/608517e187cb5bd1566b1c3728a4df0f7ac4dd5c/core/src/main/java/hudson/triggers/SCMTrigger.java#L225 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run There are a few long running git processes. Example: jenkins 743210.0 0.052568 4484 1 I+ 16Mar15 0:00.03 ssh g...@git.company.com git-upload-pack 'repoowner/reponame.git' 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run I've updated to 1.607 and we've changed some crons to a simpler */15 * * * I'll let you know. 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run It ran twice on a Saturday while that's not possible according to one of the crons: H/30 7-22 * * 1-5 The server time is correct. This is the whole System Information page: https://gist.github.com/frvge/28884e6755a2610ec2cb (removed a few IPs). We upgraded to the version with the new build layout so I'd prefer not to downgrade. With 500 jobs I don't want to take chances that something goes wrong. I can do it, but only as a last resort. Jenkins is running in a screen session. Maybe that also has something to do with it? 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Update: We just did maintenance on our gitlab server, including a start/stop of the program, and suddenly all the polling / triggers started working again. This meant a big big big queue. (which failed because we couldn't checkout the code of course). The interesting part is that a timed job, configured like 58 23 * * * also ran again automatically. Its running time is also not consistent with that schedule: Failed Console Output#16 Apr 1, 2015 6:21 PM Failed Console Output#15 Apr 1, 2015 6:05 PM Failed Console Output#14 Apr 1, 2015 6:04 PM Success Console Output#13 Apr 1, 2015 7:38 AM Success Console Output#12 Mar 30, 2015 10:24 PM Success Console Output#11 Mar 29, 2015 11:22 AM Success Console Output#10 Mar 27, 2015 9:43 PM Success Console Output#9 Mar 26, 2015 11:18 AM Success Console Output#8 Mar 25, 2015 4:22 AM Success Console Output#7 Mar 23, 2015 7:16 PM Success Console Output#6 Mar 22, 2015 10:23 AM Success Console Output#5 Mar 21, 2015 1:57 AM Success Console Output#4 Mar 20, 2015 12:59 PM Success Console Output#3 Mar 19, 2015 2:40 AM Success Console Output#2 Mar 17, 2015 8:45 PM Success Console Output#1 Mar 16, 2015 6:05 PM 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] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren created JENKINS-27677 SCM Polling does not run Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 31/Mar/15 8:49 AM Description: Our cron-based polling does not work. The UI correctly seems to say when the next and previous polling times will/would be, but the polling log isn't updated. Sometimes it's more than 3 days behind. I found this in the threadDump page: Jenkins cron thread "Jenkins cron thread" Id=25 Group=main WAITING on java.util.TaskQueue@1c75ef13 at java.lang.Object.wait(Native Method) - waiting on java.util.TaskQueue@1c75ef13 at java.lang.Object.wait(Object.java:503) at java.util.TimerThread.mainLoop(Timer.java:526) at java.util.TimerThread.run(Timer.java:505) jenkins.util.Timer [#10] "jenkins.util.Timer [#10]" Id=78 Group=main WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7f92c0bf at sun.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7f92c0bf at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1085) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) jenkins.util.Timer [#1] "jenkins.util.Timer [#1]" Id=26 Group=main WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7f92c0bf at sun.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7f92c0bf at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1085) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) jenkins.util.Timer [#2] "jenkins.util.Timer [#2]" Id=63 Group=main WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7f92c0bf at sun.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7f92c0bf at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1085) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) jenkins.util.Timer [#3] "jenkins.util.Timer [#3]" Id=66 Group=main TIMED_WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7f92c0bf at sun.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7f92c0bf at
[JIRA] [core] (JENKINS-22028) HTML in job description does not get rendered (all html tags escaped)
Frank van Gemeren commented on JENKINS-22028 HTML in job description does not get rendered (all html tags escaped) Follow-up: I couldn't find Antisamy Plugin anywhere. We fixed it by enabling "OWASP Markup Formatter Plugin". The release notes of 1.553 do not explicitly name this plugin. 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-22028) HTML in job description does not get rendered (all html tags escaped)
Frank van Gemeren reopened JENKINS-22028 HTML in job description does not get rendered (all html tags escaped) I'm having the same issue on a relatively new installation. The version number is 1.590. There is only the "Escaped HTML" option in Global Security. I can't see "Safe HTML". Any ideas? Change By: Frank van Gemeren (24/Nov/14 6:55 PM) Resolution: Fixed Status: Resolved Reopened 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-25665) API username gets set to lower-case after Jenkins restarts or force-reload
Frank van Gemeren reopened JENKINS-25665 API username gets set to lower-case after Jenkins restarts or force-reload I just read through those tickets, but I don't see why the problem only happens after a restart. That is IMO the bug. Change By: Frank van Gemeren (20/Nov/14 9:40 AM) Resolution: WontFix Status: Resolved Reopened 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-25665) API username gets set to lower-case after Jenkins restarts or force-reload
Frank van Gemeren created JENKINS-25665 API username gets set to lower-case after Jenkins restarts or force-reload Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Nov/14 3:23 PM Description: After a restart of Jenkins, API usernames that had an uppercase character are converted to lowercase. The security profile can't find permissions for this new user and blocks the connection. Before the restart, it worked OK. I'm using the built-in Jenkins database for storing users. Expected behavior: Either convert the username on user-creation time immediately to a lower-case version for API usage and make sure it never changes (or) Do not convert when restarting How to reproduce: Create a user with a capital in the name Verify that the user's API username has a capital (optional: create a security entry for this user using the username with the capital) Restart Jenkins Verify that the user's API username is now lowercase (optional: verify that logging in via API doesn't work work anymore) (optional: verify rhat after adding the lowercase-version of the API username to the security screen, everything works OK again) Addendum: Interestingly, the username used by the external tool doesn't have to be changed to the lower-case version (OpenStack's Jenkins Job Builder in my case). I'm not sure if this is because of behavior of the tool, or the behavior of the logging-in part in Jenkins. Environment: Jenkins 1.590 Ubuntu 12.04 I think, as a virtual machine Java Runtime 1.6.0_33-b33 OpenJDK 1.6 Project: Jenkins Priority: Minor Reporter: Frank van Gemeren 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.
