Legacy Knowledge Base
Published Jun. 30, 2025

Builds fail due to org.jenkinsci.plugins.github_branch_source.ApiRateLimitChecker$RateLimitCheckerAdapter checkRateLimit

Written By

Madhusudan Sharma

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • Jenkins is failing while creating the DXP cloud build and the following errors are observed:
ERROR: org.jenkinsci.plugins.github_branch_source.ApiRateLimitChecker$RateLimitCheckerAdapter checkRateLimit
ERROR: LocalChecker for rate limit was not set for this thread. Configured using system settings.

Environment

  • Liferay DXP 7.4

Resolution

ERROR: org.jenkinsci.plugins.github_branch_source.ApiRateLimitChecker$RateLimitCheckerAdapter checkRateLimit

The above error suggests that the build limit has been reached, preventing further API calls.

ERROR: LocalChecker for rate limit was not set for this thread. Configured using system settings.

As per the above, the pipeline execution wasn't configured. It's currently relying on the system-wide settings.

To resolve the above errors, we would suggest avoiding triggering builds on all branches as a workaround. This will help you save disk space and prevent unnecessary builds from running, which in turn will prevent you from exceeding your daily quota limit.
 
Please set the following environment variables in your infrastructure environment:

LCP_CI_SCM_BRANCH_FILTER_INCLUDE
LCP_CI_SCM_BRANCH_FILTER_EXCLUDE

Below is more information regarding the above environmental variables: 

LCP_CI_SCM_BRANCH_FILTER_INCLUDE - specify those branches which you WANT to trigger build
LCP_CI_SCM_BRANCH_FILTER_EXCLUDE - specify those branches which you DON'T WANT to trigger build

For example, if you want the develop and master branches to be included in the autoscan and exclude the branches that start with PR, you would have to configure it as follows:

LCP_CI_SCM_BRANCH_FILTER_INCLUDE="master develop"
LCP_CI_SCM_BRANCH_FILTER_EXCLUDE="PR-*"

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base