On Jul 22, 2012, at 11:49 PM, Justin Mclean wrote:
> Hi,
>
>> I think it should email flex-private since those are the only folks that
>> should be able to break the build.
>
>
> If it mailed the pubic list it would also tell other developers that the
> build is currently broken (which could
Hi,
> The Jenkins builds still has breakages not due to code changes.
Other then the occasional timeout (now increased) and rare HTTP issue it's been
reasonable stable for a while. Out of the last 10 build 2 timed out (should no
longer be an issue) and one failed due to a HTTP error.
> The nig
On 7/23/12 2 :33AM, "Alex Harui" wrote:
>
>
>
>On 7/22/12 2:17 AM, "Justin Mclean" wrote:
>
>> Hi,
>>
>> I've just increased the timeout with the Jenkins build to 30 minutes
>>(from 20)
>> as we've had a few timeouts. We've also just passed our 100th automated
>>build.
>>
>> With the initial
On Sun, Jul 22, 2012 at 11:49 PM, Justin Mclean wrote:
> Hi,
>
> > I think it should email flex-private since those are the only folks that
> > should be able to break the build.
>
>
> If it mailed the pubic list it would also tell other developers that the
> build is currently broken (which could
Hi,
> I think it should email flex-private since those are the only folks that
> should be able to break the build.
If it mailed the pubic list it would also tell other developers that the build
is currently broken (which could be useful if you using say nightly/latest
build) and also act as a
On 7/22/12 2:17 AM, "Justin Mclean" wrote:
> Hi,
>
> I've just increased the timeout with the Jenkins build to 30 minutes (from 20)
> as we've had a few timeouts. We've also just passed our 100th automated build.
>
> With the initial release done should have Jenkins mail the mailing list whe
Hi,
I've just increased the timeout with the Jenkins build to 30 minutes (from 20)
as we've had a few timeouts. We've also just passed our 100th automated build.
With the initial release done should have Jenkins mail the mailing list when a
build fails?
Thanks,
Justin