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

Option to notify only on the first failed build #15

Closed
natesilva opened this issue Jul 10, 2014 · 8 comments
Closed

Option to notify only on the first failed build #15

natesilva opened this issue Jul 10, 2014 · 8 comments
Labels
contributions welcome

Comments

@natesilva
Copy link

We have some jobs that run on a timed schedule. If they fail, we get notifications each time. So our #jenkins channel fills up with lots of fail messages.

It would be nice to have an option like “Notify First Failure”. That way we could get notified (once!) when the job fails, and once when the job is back to normal, using the “Notify Back To Normal” option.
@raid5
Copy link

raid5 commented Dec 10, 2014

I would love this feature as well.

@samrocketman
Copy link
Member

This feature could be implemented by providing an option to not notify slack if there has been no changes regardless of success or fail. i.e. no commits have been made since the last build.

@peergum
Copy link
Contributor

peergum commented Feb 4, 2015

That should be fairly easy. I'll try to work on that asap.

samrocketman added a commit that referenced this issue Feb 10, 2015
@samrocketman
Merge PR #46 Added option to notify repeated
94ecba0 
failure.  This is also related to the request in #15.
@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.

@muanis
Copy link

muanis commented Mar 19, 2015

Looks like this was closed by #46 , should we close this one as well?

@samrocketman
Copy link
Member

Thanks for catching that. Yeah, this one should be closed. The fix was released in slack plugin 1.7.

@dkaplan-pivotal
Copy link

Is there documentation for this somewhere? I actually would like to be notified on each failure and can't figure out how to do this.

@samrocketman
Copy link
Member

In the slack plugin 1.8.1, check first failure and repeat failures settings in the job properties.

@sghill sghill mentioned this issue Feb 15, 2019
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
6 participants
@raid5 @muanis @natesilva @samrocketman @peergum @dkaplan-pivotal