[JIRA] (JENKINS-47077) "Periodically if not otherwise run" interval does not trigger index scan

[stephen.alan.conno...@gmail.com (JIRA)]

Title: Message Title

Stephen Connolly commented on JENKINS-47077   Re: "Periodically if not otherwise run" interval does not trigger index scan Hmmm so https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/triggers/Trigger.java#L226 is responsible to call Trigger.checkTriggers periodically. https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/triggers/Trigger.java#L269 runs the triggers... but only on ParameterizedJobMixIn.ParameterizedJob (at least since this change) so how is the org folder getting triggered? Ahhh folders takes care of it itself Ok... so can people affected by this issue try running the following script in the system groovy console: for (def p in Jenkins.getInstance().allItems(com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.class)) { for (def t in p.getTriggers().values()) { if (t.tabs == null) println("${p.fullName} trigger ${t.class.name} not started"); } } If you get a report of any of the triggers not being started then that would point to an NPE in FolderCron being the root cause. NOTE: I do not expect the above to be the cause. My Jenkins is on 2.89.4 and on a newly created org folder it is fine as well as on an existing org folder, e.g. see the following three screenshots that illustrate the org folder scan being daily and the multibranch scans being daily - but at different points in time - and I had not logged into my Jenkins in over a week before taking these screenshots! Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.