[JIRA] (JENKINS-52147) Repository scan constantly checking tags, hitting rate limits

[dave.konopka@gmail.com (JIRA)]

Dave Konopka created an issue

Jenkins / JENKINS-52147 Repository scan constantly checking tags, hitting rate limits Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-06-22 18:40 Environment: Jenkins: version 2.124 github-branch-source-plugin: version 2.3.4 Operating System: Debian GNU/Linux 9 in Docker container via kubernetes-plugin Priority: Critical Reporter: Dave Konopka I have an organization set with "Discover Tags" enabled under "Github Organization". One of the repos under this project has a significant number of tags. The "Repository Events" for this repo seems to show a nearly constant loop checking the full list of tags. This is eating up our Github API requests and hitting the plugin's throttling: {{Checking tag v0.1.1 GitHub API Usage: Current quota has 1664 remaining (2 over budget). Next quota of 5000 in 22 min. Sleeping for 26 sec.}} The "checking tag XXXXX" entries keep cycling through all of the tags. We also have Branches and PR's enabled for this organization. Those does not seem to be doing the same constant polling in the repo event logs unless there is a change pushed. Is this expected behavior? Is there anyway to avoid doing so many checks for existing tags? Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[dave.konopka@gmail.com (JIRA)]

Dave Konopka updated an issue

Jenkins / JENKINS-52147 Repository scan constantly checking tags, hitting rate limits

Change By: Dave Konopka

I have an organization set with "Discover Tags" enabled under "Github Organization". One of the repos under this project has a significant number of tags. The "Repository Events" for this repo seems to show a nearly constant loop checking the full list of tags. This is eating up our Github API requests and hitting the plugin's throttling: {{Checking tag v0.1.1 }} {{ GitHub API Usage: Current quota has 1664 remaining (2 over budget). Next quota of 5000 in 22 min. Sleeping for 26 sec.}} The "checking tag XXXXX" entries keep cycling through all of the tags. We also have Branches and PR's enabled for this organization. Those does not seem to be doing the same constant polling in the repo event logs unless there is a change pushed. Is this expected behavior? Is there anyway to avoid doing so many checks for existing tags? Add Comment

[dave.konopka@gmail.com (JIRA)]

[daniel.tritone@gmail.com (JIRA)]

Daniel Martins updated an issue

Jenkins / JENKINS-52147 Repository scan constantly checking tags, hitting rate limits

Change By: Daniel Martins Attachment: tag-scanning.png

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[daniel.tritone@gmail.com (JIRA)]

Daniel Martins commented on JENKINS-52147

Re: Repository scan constantly checking tags, hitting rate limits We are being hit pretty hard by this as well. We have a couple of high-activity repositories with a few thousand tags each, and I can also see the constant tag scanning behavior in their respective "Repository Events" screen; branches are constanly being created/updated, so it's common for builds to be delayed for several minutes due to the plugin's rate limit protections. In the attached screenshot I show one of these events in which a push to some branch triggered the tag scanning behavior. I also found what it seems to be the relevant portion of the source code that seems to confirm the mentioned behavior (a push to a branch triggers the tag scanning). This behavior doesn't make much sense to me, especially for large repositories with a huge number of tags. Is there any way we can disable this behavior?

Add Comment