[JIRA] (JENKINS-52112) Private Gitea repositories are not visible

4 views
Skip to first unread message

mail@rikvanderheijden.com (JIRA)

unread,
Jun 21, 2018, 10:49:01 AM6/21/18
to jenkinsc...@googlegroups.com
Rik van der Heijden created an issue
 
Jenkins / Bug JENKINS-52112
Private Gitea repositories are not visible
Issue Type: Bug Bug
Assignee: Unassigned
Components: gitea-plugin
Created: 2018-06-21 14:48
Priority: Minor Minor
Reporter: Rik van der Heijden

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

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

jan.breuer@jaybee.cz (JIRA)

unread,
Oct 21, 2018, 1:44:02 PM10/21/18
to jenkinsc...@googlegroups.com
Jan Breuer commented on Bug JENKINS-52112
 
Re: Private Gitea repositories are not visible

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.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

Kimon.Hoffmann@lawo.com (JIRA)

unread,
Jan 29, 2019, 10:58:02 AM1/29/19
to jenkinsc...@googlegroups.com

I'm also affected by this issue.

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.

Manual verification supports this assumption, since https://gitea.server/api/v1/orgs/organization-name/repos returns the expected result for v1.6.1 ff.

jan.breuer@jaybee.cz (JIRA)

unread,
Sep 17, 2019, 8:36:02 AM9/17/19
to jenkinsc...@googlegroups.com

Works for me.

Probably fixed by https://github.com/jenkinsci/gitea-plugin/pull/11 but nobody updated this issue?

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

jan.breuer@jaybee.cz (JIRA)

unread,
Sep 25, 2019, 2:45:03 AM9/25/19
to jenkinsc...@googlegroups.com

Verified it again and it does not work for me.

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.

Reply all
Reply to author
Forward
0 new messages