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

Org folders repository folder never runs scans on repository

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: branch-api-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.101, Folders Plugin 6.3, GitHub Branch Source Plugin 2.3.2
    • Similar Issues:

      Description

      Recently updated Jenkins and all available plugins, and the Repository folder within our Organization folder stopped scanning completely. 

       

      I went so far as to delete our entire organization structure and re-create it. The organization does scan correctly on changes. The only time the repository level folder scans automatically is upon its initial creation from the creation of the organization. 

       

      Also makes little sense that the repository folder has a non-configurable interval of 1 day, while the organization folder was setup with an interval of 5 minutes. This is how the repo's trigger is defined in its config.xml:

      <spec>H H * * *</spec>
      <interval>86400000</interval>
      

      I manually changed that to match the Org folders config trigger, e.g. 

      <spec>H/12 * * * *</spec>
      <interval>300000</interval>

      and then gave Jenkins a restart. After ~5 minutes, sure enough, it's now scanning correctly. 

       

      So why on earth is the interval timer being set to such a long duration, and so dramatically different than the org's interval timer? 

        Attachments

          Issue Links

            Activity

            Hide
            hardwickj James Hardwick added a comment -

            Yea, we're in the same boat of keeping our Jenkins instance firewall'd off from the outside world, hence the polling. It's not a big deal for us since the Organization being polled has a fairly limited set of repos. 

            Every company I've ever been with has used Jenkins this way, and usually has had very legitimate reasons for doing so. I think it'd be a mistake to have a default worldview of "webhooks everywhere". Just my $.02. 

            Show
            hardwickj James Hardwick added a comment - Yea, we're in the same boat of keeping our Jenkins instance firewall'd off from the outside world, hence the polling. It's not a big deal for us since the Organization being polled has a fairly limited set of repos.  Every company I've ever been with has used Jenkins this way, and usually has had very legitimate reasons for doing so. I think it'd be a mistake to have a default worldview of "webhooks everywhere". Just my $.02. 
            Hide
            bryceman Bryce Schober added a comment -

            Count me as +1 org with a firewalled Jenkins instance that can't currently accept webhooks.

            On that point, does the Jenkins community have a guide for best-security-practices forwarding proxy setup for specific webhooks that orgs could follow?

            Show
            bryceman Bryce Schober added a comment - Count me as +1 org with a firewalled Jenkins instance that can't currently accept webhooks. On that point, does the Jenkins community have a guide for best-security-practices forwarding proxy setup for specific webhooks that orgs could follow?
            Hide
            apbenedetti Anthony Benedetti added a comment -

            Another +1 org that can't use webhooks.

            Any progress here?

            Show
            apbenedetti Anthony Benedetti added a comment - Another +1 org that can't use webhooks. Any progress here?
            Hide
            kwren Kevin Wren added a comment -

            +1, I also cant use webhooks due to firewalls (and dont have admin access to my jenkins instance). I'm assuming this isnt being worked on after 7 months of low activity?

            As anybody found a workaround in in the repo JenkinsFile?

            Show
            kwren Kevin Wren added a comment - +1, I also cant use webhooks due to firewalls (and dont have admin access to my jenkins instance). I'm assuming this isnt being worked on after 7 months of low activity? As anybody found a workaround in in the repo JenkinsFile?
            Hide
            borrrden Jim Borden added a comment -

            Another +1 for firewalls!  Our only remedy to poll and the whole arbitrary 1 day poll on a job quite a ridiculous way to set things up at that.  It took me days to figure out that there were two separate polls going on and left me wondering why I had to constantly click "scan organization now" to get the results I wanted.  

            Show
            borrrden Jim Borden added a comment - Another +1 for firewalls!  Our only remedy to poll and the whole arbitrary 1 day poll on a job quite a ridiculous way to set things up at that.  It took me days to figure out that there were two separate polls going on and left me wondering why I had to constantly click "scan organization now" to get the results I wanted.  

              People

              • Assignee:
                Unassigned
                Reporter:
                hardwickj James Hardwick
              • Votes:
                32 Vote for this issue
                Watchers:
                41 Start watching this issue

                Dates

                • Created:
                  Updated: