I have an organisation with only private repositories. When I try to create a build the list of repositories stays empty. When I type a user or organisation without private repositories, the list gets filled with the non-private repositories
Private repositories are visible from jenkins gitea-plugin only to administrator accounts in Gitea.
Creating administrator account where readonly access should be sufficiant is undesirable. It is also security risk, because in Jenkinsfile, there can be any code doing bad things to the repository.
While I initially assumed this being an issue on the gitea side (see: https://github.com/go-gitea/gitea/issues/5310), I'm now convinced that this is an issue with the Jenkins plugin, because the above mentioned issue has been fixed with Gitea v1.6.1 and the error persists.
If the jenkins account in gitea is not admin, it still can't see private repositories even if the account is listed in organisation members. It also fail to create web hooks.