From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Lars Kurth <lars.kurth.xen@gmail.com>, Tim Deegan <tim@xen.org>,
George Dunlap <dunlapg@umich.edu>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] travis: add IRC notifications
Date: Mon, 29 Feb 2016 16:56:49 -0500 [thread overview]
Message-ID: <20160229215649.GA24764@char.us.oracle.com> (raw)
In-Reply-To: <56D4B3D8.5050101@cardoe.com>
On Mon, Feb 29, 2016 at 03:10:48PM -0600, Doug Goldstein wrote:
> On 2/23/16 3:33 AM, George Dunlap wrote:
> > On Mon, Feb 22, 2016 at 7:03 PM, Konrad Rzeszutek Wilk
> > <konrad.wilk@oracle.com> wrote:
> >> On Mon, Feb 22, 2016 at 06:39:26PM +0000, Lars Kurth wrote:
> >>>
> >>>> On 22 Feb 2016, at 18:34, Doug Goldstein <cardoe@cardoe.com> wrote:
> >>>>
> >>>> On 2/22/16 11:06 AM, Ian Jackson wrote:
> >>>>> Doug Goldstein writes ("[PATCH] travis: add IRC notifications"):
> >>>>>> This will cause failed builds and when the build flips back to success
> >>>>>> to be reported to #xentest on FreeNode. The syntax of the message will
> >>>>>> be:
> >>>>>> <travis-ci> xen-project/xen#BUILDID (BRANCH - REVISION : COMMITTER)
> >>>>>> <travis-ci> Change view :
> >>>>>> https://github.com/xen-project/xen/compare/RANGE
> >>>>>> <travis-ci> Build details :
> >>>>>> https://travis-ci.org/xen-project/xen/builds/BUILDID
> >>>>>
> >>>>> I would like to give a little while for the community to comment on
> >>>>> whether this is what they want. Personally I think it's a reasonable
> >>>>> use of #xentest.
> >>>>>
> >>>>> I'm tempted to suggest that osstest reports should go there too :-).
> >>>>>
> >>>>> CCing Lars.
> >>>>>
> >>>>> Ian.
> >>>>>
> >>>>
> >>>> I'd like to see osstest reports go there as well.
> >>>
> >>> I don't have an issue with this, but as Ian pointed out, we should leave
> >>> some time for comments and then decide.
> >>
> >> Now that twitter can do more than 140 characters perhaps there as well :-)
> >
> > Just what we need -- the Register retweeting Xen, saying "CORE
> > DEVELOPERS BUNGLE COMMIT, BREAK BUILD!!!!"
> >
> > :-)
> >
> > -George
> >
>
> So before the Register starts reporting "Xen Project dying due to lack
> of email response", does anyone have any +1 or -1 to contribute to this
> change?
+1 to the IRC bot!
-1 to the Twitter bot..
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-29 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 15:13 [PATCH] travis: add IRC notifications Doug Goldstein
2016-02-22 17:06 ` Ian Jackson
2016-02-22 17:08 ` Andrew Cooper
2016-02-22 18:34 ` Doug Goldstein
2016-02-22 18:39 ` Lars Kurth
2016-02-22 19:03 ` Konrad Rzeszutek Wilk
2016-02-23 9:33 ` George Dunlap
2016-02-29 21:10 ` Doug Goldstein
2016-02-29 21:56 ` Konrad Rzeszutek Wilk [this message]
2016-03-01 18:10 ` Ian Jackson
2016-03-01 9:36 ` George Dunlap
2016-03-01 18:11 ` Ian Jackson
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=20160229215649.GA24764@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=cardoe@cardoe.com \
--cc=dunlapg@umich.edu \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=lars.kurth.xen@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).