Comment 9 for bug 885819

I would like to list exact places from which build downloads are available on https://android-build.linaro.org . Below, I give exact URLs representing the URL patterns we have in use. Some parts in them are dynamic of course (job name, build number, file name).

1. https://android-build.linaro.org/jenkins/job/linaro-android_panda/416/artifact/build/out/target/product/pandaboard/system.tar.bz2
2. http://android-build.linaro.org/builds/~linaro-android/panda/416/target/product/pandaboard/system.tar.bz2
3. https://android-build.linaro.org/builds/~linaro-android/panda/416/output/build/out/target/product/pandaboard/system.tar.bz2

#1 is Jenkins internal link (served by Jenkins, proxied by Apache), #2 & #3 are our frontend links, served by Apache directly off filesystem. And #3 is not really produced on any page any longer for few months, it is legacy one which used to be shown in one very obscure place, and I'm 99.9% positive that it wasn't posted anywhere. So, good solution would be to remove support for it altogether, then we'd have to maintain only 1 frontend link (+1 implicit jenkins' one). For the frontend link, we could use .htaccess to add needed rewrite/redirect magic, and that would be scalable solution (no need to patch central config), but that won't work for #1, which is internal "virtual" Jenkins link, so it would need to be handled by central Apache config file (of course, we can produce include file specifically for click-thru redirects).

And final note - all above is pertinent if EULA-protected builds will be still served from https://android-build.linaro.org/ . (But secure not-hosting them on https://android-build.linaro.org/ is a task on its own.)