linaro-release team mailing list archive

[Mathieu Poirier <mathieu.poirier@xxxxxxxxxxxxx>]

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).
>

-- 
You received this bug notification because you are a member of linaro-
infrastructure-drivers, which is the registrant for Linaro Android Build
Tools.
https://bugs.launchpad.net/bugs/821378

Title:
  Add md5sum for posted images

Status in Linaro Android Build Tools:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-android-build-tools/+bug/821378/+subscriptions