You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
This one is more of a question we are having when integrating JSPM into our Teamcity build process, rather than an issue directly with JSPM.
When we have been testing out switching to using JSPM as part of our build, we’ve started seeing the 'Github Rate limit' message appear do to too many requests from our build server. I’ve seen a previous issue relating to this #20 , and subsequently how to configure authorisation for Travis builds.
I was wondering how this might apply for a build server such as Teamcity and if anyone has any idea how to configure the auth to ensure this doesn’t happen. Has anyone had any experience of this, or know if this is possible?
The text was updated successfully, but these errors were encountered:
This one is more of a question we are having when integrating JSPM into our Teamcity build process, rather than an issue directly with JSPM.
When we have been testing out switching to using JSPM as part of our build, we’ve started seeing the 'Github Rate limit' message appear do to too many requests from our build server. I’ve seen a previous issue relating to this #20 , and subsequently how to configure authorisation for Travis builds.
I was wondering how this might apply for a build server such as Teamcity and if anyone has any idea how to configure the auth to ensure this doesn’t happen. Has anyone had any experience of this, or know if this is possible?
The text was updated successfully, but these errors were encountered: