Automated testing - SPAM alert

[David Kemp <dr...@chromium.org>]

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

Re: Automated testing - SPAM alert

[David Kemp <dr...@google.com>]

I agree that it needs to be there in the long run.
Currently I am running on a system that I can't expose to the outside
world, and I have to sort out some things before we can share data.
Exporting raw data to the outside world is not taken lightly.
There are some people that would get cranky if I accidentally exposed some
internal build information...

At this point I am not going to push the email without a manual audit.

I am concerned that the process needs to be moving along to get the build
clean without waiting for some of the security/legal issues.
Note that neither project currently builds clean now (as of the 22nd).



On Mon, Aug 26, 2013 at 2:32 PM, Filip Maj <fi...@adobe.com> wrote:

> 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" <dr...@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
>
>

Re: Automated testing - SPAM alert

[Filip Maj <fi...@adobe.com>]

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" <dr...@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