[JIRA] (JENKINS-60017) Gitea PR build fails if Jenkins user is not admin of the repo
Title: Message Title David Svantesson created an issue Jenkins / JENKINS-60017 Gitea PR build fails if Jenkins user is not admin of the repo Issue Type: Bug Assignee: Unassigned Components: gitea-plugin Created: 2019-11-01 10:57 Priority: Major Reporter: David Svantesson If the user that Jenkins uses to authenticate to Gitea is not admin of the repository, the Jenkins job fails when building pull request. It seem to fetch collaborators which requires admin priviliges but I don't understand why that is needed. [Gitea] Notifying pull request build status: FAILURE There was a failure building this commit [Gitea] Notified org.jenkinsci.plugin.gitea.client.api.GiteaHttpStatusException: HTTP 403/Forbidden at org.jenkinsci.plugin.gitea.client.impl.DefaultGiteaConnection.getList(DefaultGiteaConnection.java:1013) at org.jenkinsci.plugin.gitea.client.impl.DefaultGiteaConnection.fetchCollaborators(DefaultGiteaConnection.java:353) at org.jenkinsci.plugin.gitea.GiteaSCMSource.getTrustedRevision(GiteaSCMSource.java:477) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:99) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title David Svantesson edited a comment on JENKINS-59557 Re: Support Gitea required status checks I see your point now. I think this is more clear than HEAD:`Pipeline/branch` (exactly like that, not the branch name) Best would maybe be to have it configurable with possibility of using replaceable parameters, but I don't know how hard it would be to do. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202190.1569561798000.3328.1570538640623%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title David Svantesson commented on JENKINS-59557 Re: Support Gitea required status checks I see your point now. I think this is more clear than HEAD: `Pipeline/branch` Best would maybe be to have it configurable with possibility of using replaceable parameters, but I don't know how hard it would be to do. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202190.1569561798000.3326.1570538580130%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title David Svantesson commented on JENKINS-59557 Re: Support Gitea required status checks I agree `Pipeline/PR-` would be a good context. I don't understand about HEAD as that depends on what you check out. Usually tip of 'master' is considered to be 'HEAD'? It should be added there was another PR in Gitea to only have 'overall status checks'. It would still be good to change the context from Jenkins to be able to have different checks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202190.1569561798000.3221.1570530660230%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title David Svantesson created an issue Jenkins / JENKINS-59557 Support Gitea required status checks Issue Type: Improvement Assignee: Unassigned Components: gitea-plugin Created: 2019-09-27 05:23 Labels: plugin Priority: Major Reporter: David Svantesson Gitea now supports [required status checks before merge|https://github.com/go-gitea/gitea/pull/7481] and will be available in next release (Gitea 1.10.0). However because the Gitea plugin reports status checks with the context "Pipeline/PR-#" it is not possible to choose a required status check because it will alter for each PR. The number in the end should be removed from the reported context, or at least give the option to doing so. Add Comment
