-
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
[Exception] Could not build due to pharse on github PR #448
Comments
Did you try loosening the regex with wildcards? As written it wouldn't
allow return characters, etc
…On Dec 5, 2016 7:07 AM, "regardfs" ***@***.***> wrote:
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
<#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 <#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
<#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 <#4>,810
was updated/initialized on myrepo at 12/5/16 12:01 PM by null (comment)
Need help ASAP. T T
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#448>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB6Wxu5kolDPDazOgZAHputhP6dxrmJPks5rE_59gaJpZM4LEJuh>
.
|
Hi, @benpatterson, I just try with "ok to test" and ".*" , both print the same message as above. |
I think this may be the same as #450. |
@regardfs can you test 1.33.1 and see if the problem goes away? |
@regardfs do you have a "shared secret" set? |
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. |
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 |
OK good to hear @regardfs |
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
The text was updated successfully, but these errors were encountered: