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.

Sign up for GitHub

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

Jump to bottom

"Test Connection" button #28

Closed
maxlinc opened this issue Nov 20, 2014 · 6 comments
Closed

"Test Connection" button #28

maxlinc opened this issue Nov 20, 2014 · 6 comments
Labels
contributions welcome

Comments

@maxlinc
Copy link

maxlinc commented Nov 20, 2014

I've seen several Jenkins plugins with a "Test Connection" button. See the Gerrit Trigger for an example.

That would definitely be useful in this plugin to make sure you have the correct settings. I was trying to set this up and apparently specified an invalid channel. It took me a while to figure that out, since it is only in the system log, not the build log.
@pxr
Copy link

pxr commented Nov 29, 2014

+1 for this. This plugin is hard to setup correctly the first time.

@samrocketman
Copy link
Member

I don't actively develop this project. However, I am now maintaining pull requests and releases. Contributions are welcome!

@peergum
Copy link
Contributor

peergum commented Feb 6, 2015

Coming fix to do that...

@samrocketman samrocketman mentioned this issue Feb 10, 2015
Merged
samrocketman added a commit that referenced this issue Feb 10, 2015
@samrocketman
Preparing for 1.7 release
d6047eb 
New features:

* Advanced settings
  * Team domain and token can be specified per project; falls back to
    global config if not specified (#19)
  * Post a list of commits with the build notification (title and author
    of commit) (#30, #44, #45)
  * Include JUnit test summary in build notifications (#25)
* Use colors when sending a message using slack (#20, #24).  Also, the
  start notifications use the color of the last build result (#43)
* Support for authenticated proxies (#14)
* Test Connection button (#46, #28)
* Option to disable subsequent notifications on build failures (#46, #15)

Improvements:

* Report 'return to normal' on transition from unstable to success (#21)
* Improved logging.

Bug fixes:

* When changing the global slack settings the slack config in jobs are
  updated as well (#26, #12)
* Fix NullPointerException and output log message if slack is not
  configured (#35, JENKINS-26066)
@samrocketman
Copy link
Member

If you would like to be invited to https://jenkins-slack-plugin.slack.com/ for testing then just ask.

@samrocketman
Copy link
Member

This was released in 1.7 however it does not currently work. Please follow issue #51 for updates on when the fix is in for this issue. I'm closing this issue so #51 will be where you should follow updates.

@peergum
Copy link
Contributor

peergum commented Feb 25, 2015

It DOES work in the general settings section

On 2015-02-24, at 16:38, Sam Gleske notifications@github.com wrote:

This was released in 1.7 however it does not currently work. Please follow issue #51 for updates on when the fix is in for this issue. I'm closing this issue so #51 will be where you should follow updates.

—
Reply to this email directly or view it on GitHub.

@samrocketman samrocketman mentioned this issue Mar 3, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
contributions welcome
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pxr @samrocketman @maxlinc @peergum