Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53210

Scan Organisation no longer triggering project scans

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: branch-api-plugin
    • Labels:
      None
    • 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.6
    • Similar Issues:

      Description

      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.

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              bmerry Bruce Merry
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: