-
Notifications
You must be signed in to change notification settings - Fork 400
Add ability to specify GitHub events. #54
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
[FIXED JENKINS-23995] Set context for GH status
Fix issue with jobs using the CloudBees folders plugin being deleted
Some enhancements
... to deal with backward incompatible API change in github-api. The getUrl() method has changed in some of those methods to return API URL as opposed to HTML URL. This change fixes that.
|
👎 coding style changes, can't follow real changes. Plugin is not about any other event types rather then PUSH. |
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
Fix formatting.
|
👍 PUSH event seems real limited. In my setup, we just build during Tagging/Branch Creation. This makes sense for changes that go out in batch rather than individual items. |
|
This change has problems and useless complexity in every line of change, have no even enough time to comment them all. @jtillman please open and describe your issue in jira. |
|
@KostyaSha I think my issues are already described in an existing ticket: https://issues.jenkins-ci.org/browse/JENKINS-27842 |
|
@jtillman about "webhooks" vs "services" i already answered in your PR. If push ignores tags, then it other issue. Don't mix many issues in one. This PR wants add extra configurations and end user complexity without describing any real case. Allowing register many events in plugin that doesn't support this events is bad behaviour. In the same way gh plugin can do coffee. |
|
Sorry but I couldn't fully understand your last explanation. What I think that the ticket references is the ability to subscribe different jobs to different repositories and events? Briefly looking at the UI change in this PR, it seems it just adds an advanced configuration which doesn't effect the existing use case. I'd be willing to help clean it up if its just stylistic issues. I'd like to understand better your concern around having this more configurable. |
|
Events registered by this plugin incoming into this plugin, registering useless event that doesn't handled by this plugin is redundant configuration without any real case. Listener is the right direction but UI configuration in this plugin absolutely useless. |
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.
Reason?
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.
Jenkins has a bug https://issues.jenkins-ci.org/browse/JENKINS-18537 that has problems with JDK8.
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.
Is it compile time issue of your java8 or runtime of all jenkins?
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.
It's a runtime issue for Jenkins when using this plugin and running mvi hpi:run. The moment you startup Jenkins with this plugin, you should be able to see the issue.
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.
Makes sense to decrease the dependency to 1.609.1 when it gets released
|
👍 Being able to wire to more than PUSH events would be nice for me as well. |
|
|
||
| // TODO: document me | ||
| @Deprecated | ||
| public void onPost(String triggeredByUser); |
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.
|
SonarQube analysis reported 117 issues Watch the comments in this conversation to review them. Top 10 extra issuesNote: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:
|





Adds functionality to support other GitHub event types other than push. Extension of #53.