Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of omuppi1@gmail.com designates
 74.125.82.47 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
In-Reply-To: <D0127177.29941%aharui@adobe.com>
References: 
 <CACK5iZdnFghtrnD5yw_+4Pj4UjCVNJbyQGf38qrDw1xHcOk7-w@mail.gmail.com>
 <D0126587.2992E%aharui@adobe.com>
 <CACK5iZeemBUDng2YYuYo0aGkOUEk7a3c3WWcU9JPabDP7MZeHQ@mail.gmail.com>
 <D0127177.29941%aharui@adobe.com>
From: OmPrakash Muppirala <bigosmallm@gmail.com>
Date: Thu, 14 Aug 2014 14:24:25 -0700
Message-ID: 
 <CACK5iZdPJ7Wcoj5F0jEjNVb6MX5777w7iOMaBTPFeyH7zyvJZw@mail.gmail.com>
Subject: Re: Automating md5 checks
To: "dev@flex.apache.org" <dev@flex.apache.org>
Content-Type: multipart/alternative; boundary=f46d043bdabc3243d105009d89ee

--f46d043bdabc3243d105009d89ee
Content-Type: text/plain; charset=UTF-8

My understanding is that you are manually updating the installer config
with a new md5 value each time the artifact changes, is that correct?  By
letting the Jenkins job compute the checksum for the artifact, you dont
have to manually change the config file everytime.

You can still employ your technique of looking at last modified date.  My
suggestion does not require you to change that logic.

Yes, it is a one time change to the Installer itself, but after that change
you dont have to wait for the MD5 check to break, hopefully someone reports
it us and we having to change the installer config.

Thanks,
Om


On Thu, Aug 14, 2014 at 2:04 PM, Alex Harui <aharui@adobe.com> wrote:

> Still not understanding.  How would that be less work and require a new
> installer scripts?  The current SDK and FlexJS scripts are going to look
> in the config file.
>
> Also note that, to reduce bandwidth, this job stores an identifier from
> the server response headers such as the last modified date.  That way the
> job doesn't download these huge AIR SDKs over and over again unless they
> report as changed.  Even if we created separate .md5 files, we still need
> a place to track the identifiers.
>
> -Alex
>
> On 8/14/14 1:55 PM, "OmPrakash Muppirala" <bigosmallm@gmail.com> wrote:
>
> >On Thu, Aug 14, 2014 at 1:10 PM, Alex Harui <aharui@adobe.com> wrote:
> >
> >>
> >>
> >> On 8/14/14 11:08 AM, "OmPrakash Muppirala" <bigosmallm@gmail.com>
> wrote:
> >>
> >> >Alex,
> >> >
> >> >I see that there is a job
> >> >http://apacheflexbuild.cloudapp.net:8080/job/MD5Checker/
> >> >Are you using that to automatically check the MD5?
> >> Yes
> >> >
> >> >If so, you can spit out the correct MD5 into a text file and make it
> >> >available as part of the lastSuccessfulBuild/artifacts/out directory.
> >>You
> >> >can then access that file publicly with this url:
> >> >
> >>
> >>
> http://apacheflexbuild.cloudapp.net:8080/job/MD5Checker/lastSuccessfulBui
> >>l
> >> >d/artifact/out/md5.txt
> >> >
> >> >You can load this url in the Installer and verify the MD5 against the
> >> >downloaded file.
> >> >
> >> >This way, you don't need to modify the installer config every time
> >>Adobe
> >> >changes the bits.
> >> I'm not understanding.  I don't see any mention of md5.txt in Installer
> >> code base.
> >>
> >
> >That was an example file name.  You can write out the md5 checksum of the
> >artifact to a file and load it from the url.
> >
> >Thanks,
> >Om
> >
> >
> >>
> >> -Alex
> >>
> >>
>
>

--f46d043bdabc3243d105009d89ee--