Michael Nutt e8b993e7da Add support for after_success and after_failure to email notifications ... This allows you to restrict email notifications to only be sent after the build changes from success to failure or failure to success. It errs on the side of sending the notification; if the build is in another state (hung, for instance) or there was no previous build on the branch the email will also be sent. Since the notify plugin shouldn't really have any responsibility for querying the database to find the previous commit's status, we store it on the commit when we save it.		2014-12-30 11:37:57 -05:00
..
app	Serve robots.txt from /	2014-12-24 13:03:08 -06:00
blobstore	moved sql-based Blobstore to the database package	2014-09-27 13:32:54 -07:00
capability	added test for capabilities	2014-10-01 10:09:13 -07:00
datastore	Add support for after_success and after_failure to email notifications	2014-12-30 11:37:57 -05:00
handler	Wall feed	2014-11-11 10:02:18 -06:00
middleware	ability to handle options requests	2014-11-15 22:15:22 -08:00
pubsub	prevent panic when replaying on closed channel	2014-11-10 21:13:18 -08:00
router	Add feed route	2014-11-11 10:02:31 -06:00
session	minor session refactoring in prep for upcoming changes discussed in #590	2014-10-19 22:45:32 -07:00
sync	Allow sync manually, instead force sync at ever login	2014-10-28 19:51:54 +03:00
worker	Fix docker TLS, update readme and config file	2014-12-10 18:39:46 +03:00
main.go	Serve robots.txt from /	2014-12-24 13:03:08 -06:00