Skip to content

Conversation

@marcus-chan
Copy link

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

Review on Reviewable

@KostyaSha
Copy link
Member

👎 coding style changes, can't follow real changes. Plugin is not about any other event types rather then PUSH.

@jenkinsadmin
Copy link
Member

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@jtillman
Copy link

👍 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.

@KostyaSha
Copy link
Member

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.

@jtillman
Copy link

@KostyaSha I think my issues are already described in an existing ticket: https://issues.jenkins-ci.org/browse/JENKINS-27842

@KostyaSha
Copy link
Member

@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.

@jtillman
Copy link

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.

@KostyaSha
Copy link
Member

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.
Having variable for providing other variable optionally is also not good variant of UI configuration.
GitHubCause looks like a hack for his own single use case.
I split current plugin issues in 2 issues https://issues.jenkins-ci.org/browse/JENKINS-28138 and https://issues.jenkins-ci.org/browse/JENKINS-28139
And firstly i think should be resolved #39 , then migration to webhooks and finally extension.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reason?

Copy link
Author

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.

Copy link
Member

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?

Copy link

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.

Copy link
Member

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

@adepue
Copy link

adepue commented Apr 28, 2015

👍 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);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MINOR "public" is redundant in this context. rule

@dummy-lanwen-bot
Copy link

SonarQube analysis reported 117 issues

  • BLOCKER 2 blocker
  • CRITICAL 1 critical
  • MAJOR 31 major
  • MINOR 83 minor

Watch the comments in this conversation to review them.

Top 10 extra issues

Note: 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:

  1. BLOCKER Cleaner.java#L72: Catch Exception instead of Throwable. rule
  2. BLOCKER GitHubPushTrigger.java#L194: Catch Exception instead of Throwable. rule
  3. CRITICAL GitHubPushTrigger.java#L465: Make this "public static ALLOW_HOOKURL_OVERRIDE" field final rule
  4. MAJOR Cleaner.java#L64: Refactor the code to remove this label and the need for it. rule
  5. MAJOR Cleaner.java#L85: Move the "jenkins" string literal on the left side of this string comparison. rule
  6. MAJOR GitHubPushTrigger.java#L163: Add the missing @deprecated annotation. rule
  7. MAJOR GitHubPushTrigger.java#L185: Add the "@OverRide" annotation above this method signature rule
  8. MAJOR GitHubPushTrigger.java#L191: Refactor this code to not nest more than 3 if/for/while/switch/try statements. rule
  9. MAJOR GitHubPushTrigger.java#L409: Remove this use of constructor "String(byte[])" rule
  10. MAJOR GitHubPushTrigger.java#L465: Make ALLOW_HOOKURL_OVERRIDE a static final constant or non-public and provide accessors if needed. rule

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.