-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins version 2.89.4 running in native Ubuntu 16.04 environment
GitHub Branch Source Plugin 2.3.2
Our GitHub organization has over 300 repositories. In the scan log, I only see the first 300 repositories being evaluated resulting in jobs not being created for repos that come after the first 300.
Expected Results: Repositories beyond the first 300 should be evaluated and jobs should be created for them if they match the Repo/Branch/Jenkinsfile criteria
Workaround: Reduce the number of repositories in the organization to 300 or lower
[JENKINS-50747] GitHub Organization Scan only evaluates the first 300 repositories
Description |
Original:
Our GitHub organization has over 300 repositories. In the scan log, I only see the first 300 repositories being evaluated resulting in jobs not being created for these repositories. *Expected Results*: Repositories beyond the first 300 should be evaluated and jobs should be created for them if they match the Repo/Branch/Jenkinsfile criteria *Workaround*: Reduce the number of repositories in the organization to 300 or lower |
New:
Our GitHub organization has over 300 repositories. In the scan log, I only see the first 300 repositories being evaluated resulting in jobs not being created for repos that come after the first 300. *Expected Results*: Repositories beyond the first 300 should be evaluated and jobs should be created for them if they match the Repo/Branch/Jenkinsfile criteria *Workaround*: Reduce the number of repositories in the organization to 300 or lower |