Hi everyone,
In preparation for the larger Everyone permissions cleanup[1] I wrote a script determining collaborators/contributors for every plugin. Reviewing its output, I found ~40 repos that had broken team/repo associations, i.e. per-repo teams that grant access to repositories other than the named one. I expect most of these associations are due to GitHub behavior that added all of a user's teams to a repo they fork or create (one of many reasons why we fork with the bot!). I cleaned most of those up (those repos with 90+ teams associated with them -- no joke -- will need GitHub support involvement).
So, if you lost access to any of these repos today, this is the reason. Please respond to this thread, or ping me on IRC, to get your access restored, if you are a (co)maintainer of any of these:
build-with-parameters-plugin
cloudbees-disk-usage-simple-plugin
ec2-fleet-plugin
exclude-matrix-parent
github-additional-traits-plugin
graphite-plugin
html5-notifier-plugin
icescrum-plugin
image-gallery-plugin
jacoco-plugin
jna
jsch-plugin
jslint-jenkins-plugin
keep-slave-offline-plugin
leiningen-plugin
logging-plugin
Matrix-sorter-plugin
maven-license-plugin
openstack-cloud-plugin
pipeline-build-step-plugin
pipeline-model-definition-plugin
plexus-utils
pubsub-light-module
r-plugin
redmine-plugin
sahagin-plugin
saml-plugin
seleniumhtmlreport-plugin
signal-killer
sse-gateway-plugin
telerik-appbuilder-plugin
updatejob-plugin
upstream-downstream-view-plugin
These three repos have so many team associations that they break the GitHub UI (90-130 teams each), so I'm in contact with GitHub support to fix them:
emmacoveragecolumn-plugin
matrix-reloaded-plugin
selenium-tests
In general, don't reuse the autogenerated teams to set up some sort of manual team/permissions management in GitHub. Create new teams for this that are unambiguously not a autogenerated 'whatever-plugin Developers' team.
Daniel
1:
https://groups.google.com/d/msg/jenkinsci-dev/ksKAsmsmVng/lG2lNEaJBQAJ