-
Notifications
You must be signed in to change notification settings - Fork 612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jenkins Github Pull Request Builder Plugin throwing user authentication error #810
Comments
Same problem here... |
Update your credentials by providing your oauth token. It is still the same credential type - username/password, but password section should include your token. |
Thank you @bl4keee! I created a new access token and its working. |
Can you provide instruction that you were following in order to set up Github Pull Request Builder plugin? Even though token access is working good, my jobs are not being triggered on raising pull request... :/ |
+1 to this problem.
…On Wed, Mar 24, 2021 at 2:47 PM Bartosz Walczak ***@***.***> wrote:
Can you provide instruction that you were following in order to set up
Github Pull Request Builder plugin? Even though token access is working
good, my jobs are not being triggered on raising pull request... :/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#810 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGAGTXPGOCQA5KG4SP4LTMDTFGU4PANCNFSM4YSSHY3Q>
.
|
Were you able to resolve issue? Facing same issue |
+1, same for me |
same issue and resolved following the above. Thanks @bl4keee :) |
Password will be token. |
how do i generate a token? |
Follow this tutorial. I hope it helps you. |
I'm getting below error "Unable to connect to GitHub API: org.kohsuke.github.HttpException: {"message":"Requires authentication","documentation_url":"https://docs.github.com/rest/reference/users#get-the-authenticated-user"}"
Tried with multiple user on 2 different Jenkins, issue remains same.
The text was updated successfully, but these errors were encountered: