[JIRA] (JENKINS-53210) Scan Organisation no longer triggering project scans
Title: Message Title Liam Newman resolved as Fixed Jenkins / JENKINS-53210 Scan Organisation no longer triggering project scans Change By: Liam Newman Status: Open Resolved Resolution: Fixed 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.193236.1535031895000.15680.1559155080256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53210) Scan Organisation no longer triggering project scans
Title: Message Title Bruce Merry commented on JENKINS-53210 Re: Scan Organisation no longer triggering project scans This is more-or-less addressed by https://issues.jenkins-ci.org/browse/JENKINS-56917: one can now configure the project to set the polling interval for children. 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-53210) Scan Organisation no longer triggering project scans
Title: Message Title Stephen Connolly assigned an issue to Unassigned Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA Jenkins / JENKINS-53210 Scan Organisation no longer triggering project scans Change By: Stephen Connolly Assignee: Stephen Connolly 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-53210) Scan Organisation no longer triggering project scans
Title: Message Title Bruce Merry updated an issue Jenkins / JENKINS-53210 Scan Organisation no longer triggering project scans Change By: Bruce Merry Environment: OS: Ubuntu 16.04 x86-64Jenkins: 2.121.3branch-api: 2.0.20workflow-multibranch: 2.20github-branch-source: 2.3. 5 6 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53210) Scan Organisation no longer triggering project scans
Title: Message Title Bruce Merry created an issue Jenkins / JENKINS-53210 Scan Organisation no longer triggering project scans Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2018-08-23 13:44 Environment: OS: Ubuntu 16.04 x86-64 Jenkins: 2.121.3 branch-api: 2.0.20 workflow-multibranch: 2.20 github-branch-source: 2.3.5 Priority: Major Reporter: Bruce Merry We use Jenkins behind a firewall where we can't use Github event hooks, so we have a Github organisation project that periodically polls. After a Jenkins upgrade, we found updates aren't triggering builds. The problem appears to be that after the organisation scan, it is no longer scanning the individual repositories in the organisation. We can see that the timestamps in the scan log for the organisation are recent but those for each individual repository are old. Manually triggering a repository scan has the desired effect. I've set up a toy Jenkins installation and reproduced the problem with all-latest plugins. It seems to be a regression between branch-api 2.0.16 and 2.0.17: if I downgrade workflow-multibranch to 2.16 (to fix dependency problems) and switch branch-api between 2.0.16 and 2.0.17 then it works as desired with 2.0.16 but fails with 2.0.17.
