jenkins-hipchat-plugin icon indicating copy to clipboard operation
jenkins-hipchat-plugin copied to clipboard

Published 20 hours ago • verified publisher icon jlewallen

failed/still failing/fixed - options to chose when to send notifications

Open gkodesk opened this issue 12 years ago • 16 comments

hi,

recently I was using the plugin for notification the sanity check job (runs via Jenkins cron each 30 min).

so it looks kinda bored to be notified in each 30 minute about a "green line" (it usually passed)

could it be possible please to make an option to choose when to send the notifications ? (for me its ideal to have options to choose like: failed/still failing/fixed builds) - so the continuous "fixed/green" messages would be omitted.

thanks.

gkodesk avatar May 01 '12 20:05 gkodesk

+1 for me. We only want to be notified via hipchat if a build fails (or is unstable).

mvantellingen avatar Jun 11 '12 09:06 mvantellingen

See that this is already implemented in HEAD, and working just fine :-) Thanks

mvantellingen avatar Jun 11 '12 10:06 mvantellingen

+1 It would be nice to get an updated version of the plugin available via Jenkins plugin manager.

taylorleese avatar Aug 31 '12 02:08 taylorleese

+1 to @taylorleese, I could not figure out how to to compile to an .hpi file using maven... If anyone could update this in the plugin manager or provide details on how to compile this to an .hpi, please let me know!

JackCA avatar Oct 05 '12 23:10 JackCA

@JackCA build from the version here https://github.com/jenkinsci/hipchat-plugin

taylorleese avatar Oct 05 '12 23:10 taylorleese

@taylorleese How do I go about doing that? I cloned the repo onto my jenkins machine and ran mvn in the directory but get Cannot find parent: org.jenkins-ci.plugins:plugin. Sorry, I'm not much of a Java guy so I'm pretty clueless. I'm sure I'm missing something simple.

JackCA avatar Oct 06 '12 00:10 JackCA

Interesting, mvn package should build the hpi and I just pulled the latest and it seemed to work fine.

taylorleese avatar Oct 06 '12 00:10 taylorleese

Ah, we got it! We had a bad file sitting in our ~/.m2 directory. Deleting the lingering failed install file cleared that up. Thanks so much

JackCA avatar Oct 06 '12 00:10 JackCA

This doesn't seem to do "Fixed"

davedash avatar Dec 04 '12 19:12 davedash

Given that the 4fa23e10fbe878d30553da8db56fce65ce769133 has been merged, can we close this issue?

kellybyrd avatar Jun 11 '13 00:06 kellybyrd

After installing the 0.15-SNAPSHOT, I think that the issue here has been resolved. However, I would like to see an official release of 0.15, and I'm sure there are others that agree :)

cowboygneox avatar Dec 04 '13 15:12 cowboygneox

Ditto...please release this! This issue was filed 2yrs ago :-P

kenyee avatar Jan 07 '14 20:01 kenyee

A release would be very much appreciated!

johtso avatar Jan 20 '14 13:01 johtso

+1

Igorshp avatar May 30 '14 11:05 Igorshp

This is now available in v0.1.5.

CharlesHarley avatar Jun 06 '14 11:06 CharlesHarley

Is it correct that this only gives you the possibility to only be notified once when the build changes from failing to a success and not the other way? There are still no way to suppress a message every time a build fails, and therefore a recurring failing build will give recurring messages?

asjj1706 avatar Nov 15 '16 16:11 asjj1706