Add md5sum for posted images

[Mathieu Poirier]

It would but useful to convey m5d sums for boot, system and userdata posted images. The method to do relay the information is not very important to me, as long as we have it available. Whatever is the easiest for you will work for me.

[Paul Sokolovsky (pfalcon)]

Can you please elaborate why this is useful and how intended to be used?

[Botao (botao-sun)]

Sometimes, people with unstable or slow Internet connection may need this feature to check their downloads whether be exactly same as server's. In addition, if something goes wrong during the image flashing, people also can use this feature to help them find the root cause. They should check the md5sum of their downloads first. If they match with server's, at least, people know the image files are good, then they can continue to check the other parts. In a word, because the Internet environment is complex and different, people need md5sum to ensure their downloads are 100% same as server's, and this check should be the first thing to do after download.

[Paul Sokolovsky (pfalcon)]

Ok, my understanding that people care only about verifying downloads,
nothing else.

Because otherwise Jenkins has built-in "fingerprinting" support which
might serve for the purpose of identifying to which build a particular
artifact belongs. For example, consider following case: all recent
build have regression for some feature, but locally, you have known
working system.tar.bz2, but don't remember what build it was from.
Well, you could md5sum it and query fingerprint database to find out.
If Jenkins actually supports such queries. So, I hope to learn more
about that "fingerprinting", and if it's useless for us, just add
md5sum'ing at the end of build (and likely put results into MD5SUM
file, like is commonly done).

--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

[Mathieu Poirier (mathieu.poirier-deactivatedaccount)]

Good morning,

You are correct in your assesment - all I want is a way to identify the
build an image comes from. If there is a built-in DB in jenkins we
don't have to do anything. Otherwise, just a text file would serve the
purpose.

Thanks for looking into this.

Mathieu.

On 11-09-12 04:40 AM, Paul Sokolovsky wrote:
> Ok, my understanding that people care only about verifying downloads,
> nothing else.
>
> Because otherwise Jenkins has built-in "fingerprinting" support which
> might serve for the purpose of identifying to which build a particular
> artifact belongs. For example, consider following case: all recent
> build have regression for some feature, but locally, you have known
> working system.tar.bz2, but don't remember what build it was from.
> Well, you could md5sum it and query fingerprint database to find out.
> If Jenkins actually supports such queries. So, I hope to learn more
> about that "fingerprinting", and if it's useless for us, just add
> md5sum'ing at the end of build (and likely put results into MD5SUM
> file, like is commonly done).
>

[Paul Sokolovsky (pfalcon)]

Ok, played with Jenkins fingerprints, those are indeed md5sum's, but Jenkins doesn't provide way to display them visibly or export via API. So, won't work for us, will look into making MD5SUMS file.

[Paul Sokolovsky (pfalcon)]

Ok, please have a look at https://android-build.linaro.org/jenkins/job/linaro-android_panda/292/ (file MD5SUMS) and see if that covers your needs.

[Botao (botao-sun)]

Hi Paul, I don't find the md5sum section on "staging-origen" build: https://android-build.linaro.org/builds/~linaro-android/staging-origen/

[Paul Sokolovsky (pfalcon)]

Sorry, final deployment was kinda lost in action. Enabled for all builds, will be available after this night's rebuild (or on manual rebuild of course).