On Tue, Jul 22, 2014 at 11:26 PM, Alex Harui <aha...@adobe.com> wrote:

>
>
> On 7/22/14 4:10 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>
> >On Tue, Jul 22, 2014 at 4:01 PM, Justin Mclean <jus...@classsoftware.com>
> >wrote:
> >
> >> Hi,
> >>
> >> > That's why I asked about some sort of Jenkins job that could catch
> >> changes.
> >>
> >> Probably not the best idea IMO. If Jenkins get it wrong we break the
> >> installer for everyone. The downloads have never failed for Jenkins
> >>before
> >> right? :-)
> >>
> >>
> >That is exactly my concern.  I don't think we should be in the business of
> >verifying downloads from external servers.
>
> Makes sense, but the fact is the current situation is that we are trying
> to get Ant to fail gracefully (instead of just throwing an exception) when
> it tries to unzip a bad download for which there is no MD5 to check
> against, and the bits get updated periodically.


Ant ant or ant_for_air?  If it is ant_for_air, I imagine we can just listen
to exceptions and react accordingly, right?


> I'm open to other ideas.
>
>
Any chance you can get the Flash Player team to upload MD5 checksums for
the artifacts they upload?  It should not be a very hard thing to do for
them.

Thanks,
Om


> -Alex
>
>

Reply via email to