jenkinsci / jenkinsci/github-branch-source-plugin

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

Open
#1,190 4 comments 0 reactions 0 assignees View on GitHub
component:github-branch-source-plugin imported-jira-issue priority:critical resolution:unresolved
Dominant language
Java
Stars
217
Forks
398
Avg merge
30m
Merged PRs (30d)
1

Description

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?

---
Originally reported by davekonopka, imported from: Repository scan constantly checking tags, hitting rate limits


  • status: Open
  • priority: Critical
  • component(s): github-branch-source-plugin
  • resolution: Unresolved
  • votes: 5
  • watchers: 10
  • imported: 2025-12-02

Raw content of original issue

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?

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

```

1 attachment

- [tag-scanning.png](https://issues.jenkins.io/secure/attachment/47300/tag-scanning.png)
> ![tag-scanning.png](https://issues.jenkins.io/secure/attachment/47300/tag-scanning.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.