Skip to content
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

add baseUrl parameter to support slack-compatible integrations #204

Closed
wants to merge 3 commits into from

Conversation

andrzejwp
Copy link

Solution for #174 - additional configuration parameter to specify the full URL (before token) to support slack clones with compatible API, e.g. rocket.chat.

@jenkinsadmin
Copy link
Member

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

@chkal
Copy link

chkal commented Mar 25, 2016

I'm not very familiar with Jenkins plugins, but as I'm interested in the feature, I just reviewed the PR. Looks very good to me. 👍

final String sendAs, final boolean startNotification, final boolean notifyAborted, final boolean notifyFailure,
final boolean notifyNotBuilt, final boolean notifySuccess, final boolean notifyUnstable, final boolean notifyBackToNormal,
final boolean notifyRepeatedFailure, final boolean includeTestSummary, CommitInfoChoice commitInfoChoice,
boolean includeCustomMessage, String customMessage) {
super();
this.baseUrl = baseUrl;
Copy link
Member

Choose a reason for hiding this comment

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

Perhaps trim off potential spaces. Just trimming here should be enough for other instances where SlackNotifier is used.

@samrocketman
Copy link
Member

👎 for the issues I pointed out. Other than that, looks good.

@andrzejwp
Copy link
Author

Hi, I followed exactly how other parameters are handled. There is no trimming there, so I can either leave it without trimming, or we should trim all of them?
Thanks for the catch with the incorrect if() statement, I missed that.

@samrocketman
Copy link
Member

I would say correct the trimming associated with this change and then a second pull request can be created to address trimming all of the other values. In general, I prefer to trim and sanitize human input as much as possible.

I'll defer to @kmadel for the actual merge.

@Reamer
Copy link
Contributor

Reamer commented Aug 15, 2016

👍 works. Thanks

@kmadel
Copy link
Contributor

kmadel commented Aug 25, 2016

Needs help text. Also, and example in the README would be nice.

@MitchTalmadge
Copy link

👍 Any news on this?

@samrocketman
Copy link
Member

I plan on performing a release this weekend. If you would like this PR to be in it then please rebase/resolve. Also, please add help text for the option so users know what it is for.

@samrocketman
Copy link
Member

This PR is superseded by #293.

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.

7 participants