Pull requests are not triggered on comment triggers ( >= 1.32.4)
See original GitHub issueHaving upgraded from 1.32.3 to .4 and .5, and having done a lot of extensive testing, I have found that the comment triggers no longer work. The logs clearly show that there is some difference in the paging of the comments. This behavior is observed irrespective of the value of “Only use trigger phrase for build triggering”
Here is a selected output from the log. I use the same trigger phrase for both. I have made sure that I make new comments too.
v1.32.3
Running trigger for arrayfire-linux/pr-build-tester
Jun 14, 2016 9:46:01 PM INFO org.jenkinsci.plugins.ghprb.GhprbPullRequest updatePR
Pull request #17 was updated/initialized on shehzan10/arrayfire at 6/14/16 9:44 PM by Shehzan Mohammed (PR update)
Jun 14, 2016 9:46:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Checking for comments after: 6/14/16 9:14 PM
Jun 14, 2016 9:46:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 8:46 PM
Jun 14, 2016 9:46:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:00 PM
Jun 14, 2016 9:46:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:03 PM
Jun 14, 2016 9:46:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:11 PM
Jun 14, 2016 9:46:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:14 PM
Jun 14, 2016 9:46:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:44 PM
Jun 14, 2016 9:46:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made after last update time, build arrayfire linux tester ci
Jun 14, 2016 9:46:02 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
[Shehzan Mohammed] Added comment: build arrayfire linux tester ci
Jun 14, 2016 9:46:02 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Trigger phrase
Jun 14, 2016 9:46:02 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Admin User:shehzan10 ran trigger phrase
Jun 14, 2016 9:46:02 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Running the build
Jun 14, 2016 9:46:02 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
PR is not null, checking if mergable
Jun 14, 2016 9:46:02 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Running build...
v1.32.5
Running trigger for arrayfire-linux/pr-build-tester
Jun 14, 2016 10:02:00 PM INFO org.jenkinsci.plugins.ghprb.GhprbPullRequest updatePR
Pull request #17 was updated/initialized on shehzan10/arrayfire at 6/14/16 10:01 PM by Shehzan Mohammed (PR update)
Jun 14, 2016 10:02:00 PM INFO org.jenkinsci.plugins.ghprb.GhprbPullRequest updatePR
Pull request #17 was updated on repo shehzan10/arrayfire but there aren't any new comments nor commits; that may mean that commit status was updated.
Jun 14, 2016 10:02:00 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Trigger only phrase but we are not triggered
Jun 14, 2016 10:02:00 PM FINE org.jenkinsci.plugins.ghprb.GhprbTrigger
Just to be extra sure, I downgraded again to 1.32.3 and added a new comment trigger, and it works. You can notice the timestamps of the comments too between the 3 logs. Downgrade to v1.32.3
Running trigger for arrayfire-linux/pr-build-tester
Jun 14, 2016 10:16:01 PM INFO org.jenkinsci.plugins.ghprb.GhprbPullRequest updatePR
Pull request #17 was updated/initialized on shehzan10/arrayfire at 6/14/16 10:14 PM by Shehzan Mohammed (PR update)
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Checking for comments after: 6/14/16 10:01 PM
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 8:46 PM
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:00 PM
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:03 PM
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:11 PM
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:14 PM
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 9:44 PM
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 10:01 PM
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made at: 6/14/16 10:14 PM
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Comment was made after last update time, build arrayfire linux tester ci
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
[Shehzan Mohammed] Added comment: build arrayfire linux tester ci
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Trigger phrase
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Admin User:shehzan10 ran trigger phrase
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Running the build
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
PR is not null, checking if mergable
Jun 14, 2016 10:16:01 PM FINEST org.jenkinsci.plugins.ghprb.GhprbPullRequest
Running build...
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:18 (2 by maintainers)
Top Results From Across the Web
Troubleshooting why pull requests are not triggering jobs on ...
A user who submits a pull request to your repository from a fork, but no pipeline is triggered with the pull request. This...
Read more >Why will this not trigger on a pull request push commit update?
I have created a pull request. I updated some code on the branch and pushed, but the actions is not triggering? How does...
Read more >Github Actions workflow for merged/closed PRs - Max Brenner
A little guide on how to trigger Github Actions workflows when a PR has been ... I was especially interested in the pull...
Read more >Solved: Is there a trigger for a pull request that is Comm...
I would suggest to create individual triggers for finishing a PR with "Comment", and "Request Changes". And I would also rename the "Declined"...
Read more >The default GitHub Triggers builds refs/pull/<issue>/head but ...
2. refs/pull/<issue-no>/merge - this has the code from merging the pull request into master. The default trigger runs over 1 only.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same issue here. Appears to have broken in 1.32.4
I’m seeing this issue in 1.40.0, it sometimes takes multiple comments in order for a build to successfully start. This probably needs to be reopened.