Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates
 64.18.1.21 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Mon, 26 Aug 2013 11:32:36 -0700
Subject: Re: Automated testing - SPAM alert
Thread-Topic: Automated testing - SPAM alert
Thread-Index: Ac6iiqU0x1rK8yx9TJy/lCmkNSDmeA==
Message-ID: <CE40ED32.24359%fil@adobe.com>
In-Reply-To: 
 <CAMTxO41uJF4MHn1Nhhe3PQzsQD43f3b4xLpPmxaTMTKzNivcWA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.6.130613
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

What about setting up a webpage (o I dunno, ci.cordova.io) where we could
check the status of the latest builds at our own leisure?

On 8/26/13 11:30 AM, "David Kemp" <drkemp@chromium.org> wrote:

>Hi all,
>I now have an automated testing system running and testing with Android
>and
>iOS devices. It currently tests 3.0.x and 'tip-of-tree' on each of the
>projects.
>
>This means that when people commit things that break the build I will get
>a
>notification.
>
>I can send out the details on the list and share the gory details, but I
>am
>probably not going to invest a lot of time in trying to track down exactly
>what part of the commit is at issue.
>
>Does anyone have any great ideas on how they want to be SPAMmed?
>
>David Kemp