From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtG66-0007as-Dp for qemu-devel@nongnu.org; Wed, 18 Dec 2013 07:19:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VtG61-0007dq-Bu for qemu-devel@nongnu.org; Wed, 18 Dec 2013 07:19:30 -0500 Received: from static.88-198-71-155.clients.your-server.de ([88.198.71.155]:60044 helo=socrates.bennee.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtG61-0007dl-5H for qemu-devel@nongnu.org; Wed, 18 Dec 2013 07:19:25 -0500 References: <87bo0ez95h.fsf@linaro.org> From: Alex =?utf-8?Q?Benn=C3=A9e?= In-reply-to: Date: Wed, 18 Dec 2013 12:19:25 +0000 Message-ID: <878uviz702.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] Enabling Travis for the QEMU Mirror? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers , Anthony Liguori peter.maydell@linaro.org writes: > On 18 December 2013 11:32, Alex Bennée wrote: >> Now we have a .travis.yml merged into master can we enable Travis to run >> in the QEMU mirror on github (https://github.com/qemu/qemu)? I'm happy >> to talk who ever controls that repo through the process > > That would be Anthony, I think. > >> but it's fairly simple. From the commit: >> >> "This adds a build matrix definition for travis-ci.org continuous >> integration service. It is usable on any public repository hosted on >> GitHub. Once you have created an account signed into Travis you can >> enable it on selected projects via travis-ci.org/profile. Alternatively >> you can configure the service hooks on GitHub via the repository >> Settings tab,then Service Hooks and selecting Travis." >> >> Basically you just need to go to http://travis-ci.org and click the >> "Sign in with GitHub" link and your up and running. It's super easy. > > So this would get us I guess automatic build tests and a page > somewhere with current status, right? We might want to talk > about automated email-on-build-failure at some later point but > running it without that to start seems a good first step. Yes, the rest like notifications or IRC bots can be configured. We might want to convert the top level README to a README.md and insert a fancy icon link like I have in my other repos: https://github.com/stsquad/emacs_chrome#hacking > Do you have a link to a results page for what this looks like? > (IIRC you've enabled it for your private repo). Sure have a gander at: https://travis-ci.org/stsquad/qemu and https://travis-ci.org/stsquad/qemu/branches etc... > > thanks > -- PMM -- Alex Bennée QEMU/KVM Hacker for Linaro