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).
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 www.facebook. com/pages/ Linaro twitter. com/#!/ linaroorg - http:// www.linaro. org/linaro- blog
Follow Linaro: http://
http://