adriaanm
commented
9 years ago to elaborate on the commit message, we use jenkins parameters in the names & refs for the repos in all jobs, and the jenkins github oauth2 plugin seems to be having trouble with those:
`Jun 29 17:26:14 ip-172-31-3-245 [jenkins]: WARNING: Looks like a bad github URL OR the Jenkins user does not have access to the repository${repo_user}/${repo_name}``
since global security on jenkins is configured to "Use Github repository permissions "
Help for feature: Use Github repository permissions If checked will use github repository permissions to determine jenkins permissions for each project. Public projects - all authenticated users can READ. Only collaborators can BUILD, EDIT, CONFIGURE or DELETE. Private projects, only collaborators can READ, BUILD, EDIT, CONFIGURE or DELETE
i assume it's iterating through all repo's, but not finding any because it doesn't subst in the defaults for those params
so it decides user is not authenticated, unless overridden by the admin user list
which now spells his username correctly
we should figure out a way to avoid needing admin privileges, since all we should be doing with jenkins is hitting (re)build on jobs and (dis)connecting workers
all scala/scala collaborators should be allowed this
the symptom was that http://scala-ci.typesafe.com loaded very quickly for me when I wasn't logged in, but after logging in, it would take 1+ minutes to load or would sometimes just time out with a "504 Gateway Time-out" page from nginx. during the delay,
/var/log/messageson the server was printing lots of lines likeJun 29 17:26:14 ip-172-31-3-245 [jenkins]: WARNING: Looks like a bad github URL OR the Jenkins user does not have access to the repository${repo_user}/${repo_name}