janinko
Can you trigger a build from an edit to the PullLongDescription?
I have been looking at using a Github pull request template to set up a default task list for my developers based on this: https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/
One of the tasks in the list would be a checkbox for "Run Jenkins Build". The pull request builder will notify Jenkins of any changes to the pull request anyway but I only want it to run a specific job when that checkbox has been marked by a developer.
I've had a play with the Trigger phrase to be something like:
.[x]\W+run\W+jenkins\W+build.
Which should pick up the checked text box only. However it doesn't appear that pull requests are triggering of the "edited" action? I had and error stating that "edited" was an unknown action for a while but I updated the plugin and that went away (now on 1.33.1 from 1.33.0).
- If I add a NEW comment to the pull request with the checkbox unchecked it doesn't trigger the build as expected.
- If I check the checkbox on an existing comment it doesn't trigger the build either.
- If I add a NEW comment to the pull request with the checkbox ticked it does trigger the build.
I'm assuming the builder only uses the trigger phrase on a new comment? I'm having a read through the source but haven't got my head round it all yet
If it could trigger on an edit comment could it also do so on the content of the ghprbPullLongDescription as that would be where the checkboxes are being created by the template?
Currently if you attempt to edit the pull long description rather than a normal comment you get this in the log:
Pull request #34 was updated on repo ****** but there aren't any new comments nor commits; that may mean that commit status was updated.
I guess that means that the ghprb isn't looking at the long description for anything anyway?
Cheers,
Chris.
