Skip to content
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

[Exception] Could not build due to pharse on github PR #448

Closed
regardfs opened this issue Dec 5, 2016 · 8 comments
Closed

[Exception] Could not build due to pharse on github PR #448

regardfs opened this issue Dec 5, 2016 · 8 comments

Comments

@regardfs
Copy link

regardfs commented Dec 5, 2016

Need help:
When I leave a message "ok to test" on my PR(already set triggerPhrase('^ok to test$)), It could not trigger build but only below message print:
Dec 05, 2016 12:01:46 PM org.jenkinsci.plugins.ghprb.GhprbRootAction handleAction
INFO: Checking issue comment 'ok to test for web' for repo myrepo
Dec 05, 2016 12:01:46 PM org.jenkinsci.plugins.ghprb.GhprbTrigger handleComment
INFO: Checking comment on PR #4,810 for job pull-request-test-builder-identify
Dec 05, 2016 12:01:46 PM org.jenkinsci.plugins.ghprb.GhprbPullRequest updatePR
INFO: Pull request #4,810 was updated/initialized on myrepo at 12/5/16 12:01 PM by null (comment)
Dec 05, 2016 12:01:46 PM org.jenkinsci.plugins.ghprb.GhprbTrigger handleComment
INFO: Checking comment on PR #4,810 for job genric-ft-pull-request
Dec 05, 2016 12:01:46 PM org.jenkinsci.plugins.ghprb.GhprbPullRequest updatePR
INFO: Pull request #4,810 was updated/initialized on myrepo at 12/5/16 12:01 PM by null (comment)
Need help ASAP. T T

@benpatterson
Copy link
Member

benpatterson commented Dec 5, 2016 via email

@regardfs
Copy link
Author

regardfs commented Dec 6, 2016

Hi, @benpatterson, I just try with "ok to test" and ".*" , both print the same message as above.
I think it is not concern with regex.

@ilovezfs
Copy link

ilovezfs commented Dec 6, 2016

I think this may be the same as #450.

@ilovezfs
Copy link

ilovezfs commented Dec 6, 2016

@regardfs can you test 1.33.1 and see if the problem goes away?

@ilovezfs
Copy link

ilovezfs commented Dec 6, 2016

@regardfs do you have a "shared secret" set?

@benpatterson
Copy link
Member

I haven't been able to reproduce this issue. Could you make sure that the user making the comment is an admin? That's my best guess at this point.

@regardfs
Copy link
Author

Hi, I had never reproduce this problem again. It worked fine now just after a jenkins restart.Thanks u a lot for your guys help.@benpatterson , @ilovezfs

@benpatterson
Copy link
Member

OK good to hear @regardfs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants