qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: alex.bennee@linaro.org
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v1 4/4] .travis.yml: add IRC notifications for build failures
Date: Thu, 20 Feb 2014 15:37:16 +0000	[thread overview]
Message-ID: <1392910636-17338-5-git-send-email-alex.bennee@linaro.org> (raw)
In-Reply-To: <1392910636-17338-1-git-send-email-alex.bennee@linaro.org>

From: Alex Bennée <alex.bennee@linaro.org>

I'm trying to avoid spamming the IRC channel (not overly likely as
builds take a while). So failure will always be reported but if the
build continues to work then the IRC notifications will be quiet.

Note any GitHub based repository with Travis enabled will use this
notification. If it proves to be too spammy we may want to ask users not
to use Travis themselves although this seems sub-optimal.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>

diff --git a/.travis.yml b/.travis.yml
index 0dbf2da..04da973 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -4,6 +4,12 @@ python:
 compiler:
   - gcc
   - clang
+notifications:
+  irc:
+    channels:
+      - "irc.oftc.net#qemu"
+    on_success: change
+    on_failure: always
 env:
   global:
     - TEST_CMD="make check"
-- 
1.9.0

  parent reply	other threads:[~2014-02-20 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 15:37 [Qemu-devel] [PATCH v1 0/4] Updates for Travis testing alex.bennee
2014-02-20 15:37 ` [Qemu-devel] [PATCH v1 1/4] .travis.yml: add a new build target with non-core devlibs alex.bennee
2014-02-20 15:37 ` [Qemu-devel] [PATCH v1 2/4] .travis.yml: re-enable lttng user space trace test alex.bennee
2014-02-20 15:37 ` [Qemu-devel] [PATCH v1 3/4] .travis.yml: trivial whitespace fixup alex.bennee
2014-02-20 15:37 ` alex.bennee [this message]
2014-02-24 15:41 ` [Qemu-devel] [PATCH v1 0/4] Updates for Travis testing Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1392910636-17338-5-git-send-email-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).