[Ci-users] Setting Github Access token not resolving Github API rate limit error
brian at bstinson.com
Fri Feb 3 09:02:01 UTC 2017
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
On Feb 03 11:10, Budh Gurung wrote:
> A week ago, CI-admin had added our requested github token for 'minishift'
> to the credential store .
> However, assuming things will go as expected, we are still facing
> "Github API rate limit" error in our builds .
> We tried to debug with adding stdout logs (see below at time in build
> console log ) 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
> access as we are new to JJB approach.
>  https://github.com/minishift/minishift
>  https://github.com/minishift/minishift-ci-jobs/pull/11
>  https://ci.centos.org/job/minishift/88/console (same with #86, #87)
>  https://ci.centos.org/job/minishift/83/console (same with #81)
> Budh Ram Gurung
> Software Engineer - Devtools
> Ci-users mailing list
> Ci-users at centos.org
More information about the Ci-users