[Ci-users] Setting Github Access token not resolving Github API rate limit error

Brian Stinson brian at bstinson.com
Fri Feb 3 09:02:01 UTC 2017


Check Here:
https://github.com/minishift/minishift/blob/04b0411dfe2aeeb8b663e50ee651150f21c2ceee/centos_ci.sh#L25

GH_TOKEN should make it into your jenkins-env file, but that 'grep' will
ignore it and it won't get set in the environment on the duffy node.

Be sure to `set +x` right before if you decide to include it so you don't leak to the
console.

--Brian

On Feb 03 11:10, Budh Gurung wrote:
> Hi,
> 
> A week ago, CI-admin had added our requested github token for 'minishift'
> [1]
> to the credential store [2].
> 
> However, assuming things will go as expected, we are still facing
> "Github API rate limit" error in our builds [3].
> 
> We tried to debug with adding stdout logs (see below at time in build
> console log [4]) in our code and found token empty.
>     - *00:00:53.627*
> * - **00:07:04.759*
> 
> Also, suggests us the proper way to debug in this type of scenarios with no
> UI
> access as we are new to JJB approach.
> 
> [1] https://github.com/minishift/minishift
> [2] https://github.com/minishift/minishift-ci-jobs/pull/11
> [3] https://ci.centos.org/job/minishift/88/console (same with #86, #87)
> [4] https://ci.centos.org/job/minishift/83/console (same with #81)
> 
> 
> Regards,
> Budh Ram Gurung
> Software Engineer - Devtools

> _______________________________________________
> Ci-users mailing list
> Ci-users at centos.org
> https://lists.centos.org/mailman/listinfo/ci-users




More information about the Ci-users mailing list