-
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
"Only use trigger phrase for build triggering" does not work when "trigger phrase" is common with "test phrase" or "add to whitelist" phrase #499
Comments
For the record, unfortunately this issue seems to be still present and we are hitting it too. |
I'm just here in hope to understand the intended difference between Looking at ghprb-plugin/src/main/java/org/jenkinsci/plugins/ghprb/GhprbPullRequest.java Lines 610 to 630 in 57f12d0
they seem equivalent but only triggerPhrase sets triggered = true .Later in tryBuild() :ghprb-plugin/src/main/java/org/jenkinsci/plugins/ghprb/GhprbPullRequest.java Lines 521 to 524 in 57f12d0
=> So my impression is that Now, for this issue:
and later:
so I was thinking these are 2 distinct phrases, trigger vs retest? So yes, if same string matches both retest and trigger phrase, But it sounds best to configure regexps such that only one can match a given comment. |
When enabling "Only use trigger phrase for build triggering" PR builds no longer work when the trigger phrase is provided.
The trigger phrase does in fact work when "Only use trigger phrase for build triggering" is unchecked/disabled.
The trigger phrase works fine when
<onlyTriggerPhrase>true</onlyTriggerPhrase>
is set to false. As soon as the trigger phrase is required, the PR's are not built.Here's a logging example of the behavior with the option enabled, and without the option enabled:
=== With “Only use trigger phrase for build triggering" enabled ===
=== Without “Only use trigger phrase for build triggering" enabled ===
Some more details -- when trying to use the retest phrase it claims that the target branch is either not listed in the whitelist, even though it is -- or that it is not triggered. I haven't been able to figure out the context of the logs in regard to which job/branch the PR poll is performed for/by.
Is this plugin only supported to be used as a single Jenkins project for PR builds against an entire github repo? We have separate jobs created for each branch, in our configuration.
From the master branch PR builder job's config.xml:
=== From the org.jenkinsci.plugins.ghprb.GhprbPullRequest logger: ===
=== Another run ===
The text was updated successfully, but these errors were encountered: