to reply myself: perhaps there is something like a quota? i stopped the ci-runner for about 5hours and restarted it ... now it works again.
did anyone repair something or is there a quota? it its a quota, how should i work around this? the cirunner polls the gitlab.com/ci server every few seconds (in my case every 10secs). what would be the recommended interval to work around the quota? Am Sonntag, 2. Oktober 2016 20:34:11 UTC+2 schrieb Ulrich Schreiner: > > hi, > > i have a private ci-server registered with my project on gitlab.com. > since today afternoon (Oct 2nd, about 14UTC) my CI server always logs: > > Dialing: tcp gitlab.com:443 ... > WARNING: Checking for builds... failed runner=.... status=429 > Too Many Requests > > i'm running gitlab/gitlab-runner:latest as a docker-image. > > anything i can do? > > </usc> > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/88415098-c8fd-4f2b-88fc-f9cbb077745a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
