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

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

Open
gkodesk opened this issue May 1, 2012 · 16 comments
Open

Comments

@gkodesk
Copy link

gkodesk commented May 1, 2012

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.

@mvantellingen
Copy link

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

@mvantellingen
Copy link

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

@taylorleese
Copy link
Collaborator

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

@JackCA
Copy link

JackCA commented Oct 5, 2012

+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!

@taylorleese
Copy link
Collaborator

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

@JackCA
Copy link

JackCA commented Oct 6, 2012

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

@taylorleese
Copy link
Collaborator

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

@JackCA
Copy link

JackCA commented Oct 6, 2012

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

@davedash
Copy link

davedash commented Dec 4, 2012

This doesn't seem to do "Fixed"

@kellybyrd
Copy link
Collaborator

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

@cowboygneox
Copy link

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

@kenyee
Copy link

kenyee commented Jan 7, 2014

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

@johtso
Copy link

johtso commented Jan 20, 2014

A release would be very much appreciated!

@Igorshp
Copy link

Igorshp commented May 30, 2014

+1

@CharlesHarley
Copy link

This is now available in v0.1.5.

Palmr pushed a commit to Palmr/jenkins-hipchat-plugin that referenced this issue May 26, 2015
@asjj1706
Copy link

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?

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

No branches or pull requests