Hello,
Based on previous discussion, some simplifications and clarifications were done to Android publishing process:
1. When first (usually only) group of files is published, it must include BUILD-INFO.txt which gives permissions for all files which will be published as artifacts.
2. If there's 2nd group of files to publish (the only case we have is to publish lava-job-info metadata file), it must NOT include BUILD-INFO.txt, and ACLs for it must be set in the main BUILD-INFO.txt file (step 1).
3. BUILD-INFO.txt is not rewritten or altered in nay way. Again, it must include complete and final ACLs for all artifact files in a build. linaro-license-protection app as running on snapshots.linaro.org will use verbatim content of BUILD-INFO.txt as provided by the build authors to control access to the files.
Hope this clarifies access control setup greatly and resolves cases where we couldn't control some access aspects of private builds.
Now, looking at "open" builds BUILD-INFO overlays, (https://snapshots.linaro.org/android/binaries/open/) I see that
https://snapshots.linaro.org/android/binaries/open/20131212/build-info.tar.b... has complicated file pattern comparing to previous incarnation, https://snapshots.linaro.org/android/binaries/open/20131008/build-info.tar.b... which has just: ------- Files-Pattern: * License-Type: open -------
I'm not sure which prompted to prepare 20131212/build-info.tar.bz2 , but if it was done as a workaround to previous publishing problems, I'd suggest to switch back to 20131008/build-info.tar.bz2 .
Please let us (me, Milo) know if spot any issues with ACL with new publishing settings, or need help with ACLs for private builds.
Thanks, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog