-
Notifications
You must be signed in to change notification settings - Fork 400
[JENKINS-28139] Hook payload parse extension point #60
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
Conversation
add javadocs add simple test for filtering by trigger
- default push event test - hook match predicate
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
|
Tested over real GH Log: |
0ad46c2 to
2fb85d6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
align
|
The new code looks good, but there are massive changes affective binary compatibility My proposal:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
binary compatibility issue
It was planned to resolve #39 after hook extensions (that is more critical than workflow). Also i have not answered question #59 (comment) about workflow requirements meaningfulness |
[JENKINS-28139] Hook payload parse extension point
|
@KostyaSha are you rejecting a PR because there is one absolutely out-of-scope unanswered question? Workflow is what it is, such question must be done in the mailing list, not in a review comment that nothing has to do with it. If there is any other reason to not merge #59, please let me know. I'll be happy to discuss it in the dev mailing list. |
|
out-of-scope? You are extending interfaces to functionality that is not supported by this plugin. Better fix your workflow plugin and all plugins will be supported automatically. |
@KostyaSha seems you've forgotten something... |
|
@KostyaSha That's why it's out-of-scope here, you are talking about "fixing" workflow plugin, so not related to github plugin. Workflow plugin is OSS, so feel free to send a PR and the maintainer will decide about it (just like you are doing here). Just to be clear, is that unanswered question the only thing currently blocking the merge of #59? |
|
@amuniz i don't care about workflow and it's maintainer. Any plugin may accept this weird workflow changes or may ignore. As i already mentioned i see no real technical reasons for supporting Job that is casted to AbstractProject in first line.
This question plus code itself. |
|
@KostyaSha could you point me to that "cast to AbstractProject in first line" in #59? I don't see it. What do you think if we call for a #59 merge/not-merge vote in developers mailing list? |
Seems it was removed.
Funny way of resolving question - ask people absolutely unrelated for this plugin support.
Could you stop offtop? This PR is about hooks changing, it implemented and merged. |
It was not an off-top. I've requested a release of ongoing changes before merging this big thing. You will have to bump the version to 2.0, hence the aggregation of bugs is required |
JENKINS-28139
continue of #57 with extension to parse any type of GH hook
onEvent(GHEvent event, String payload)inorg.jenkinsci.plugins.github.extension.GHEventsSubscriberclassthis method can be overrided to provide any logic to reuse webhook payload