Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-16 Thread Alexander Sack
On Tue, Jul 12, 2011 at 10:13 AM, John Rigby john.ri...@linaro.org wrote: On Tue, Jul 12, 2011 at 1:07 AM, Ricardo Salveti ricardo.salv...@linaro.org wrote: On Mon, Jul 11, 2011 at 6:18 PM, Alexander Sack a...@linaro.org wrote: On Mon, Jul 11, 2011 at 4:11 PM, Zach Pfeffer

Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-14 Thread Paul Sokolovsky
Hello John, On Tue, 12 Jul 2011 02:13:40 -0600 John Rigby john.ri...@linaro.org wrote: [] If I read the prior emails correctly then the commit needs to be reachable by a head but not necessarily the head as in master so I believe that I can still rebase master (or whatever) as long as

Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-13 Thread Dechesne, Nicolas
On Tue, Jul 12, 2011 at 9:07 AM, Ricardo Salveti ricardo.salv...@linaro.org wrote: Is there other way to fix this at the tool instead of forcing the component tree owner to not rebase the tree? if the problem is that you rely on external maintainers to 1) create a tag or a ref that reaches

Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-12 Thread Ricardo Salveti
On Mon, Jul 11, 2011 at 6:18 PM, Alexander Sack a...@linaro.org wrote: On Mon, Jul 11, 2011 at 4:11 PM, Zach Pfeffer zach.pfef...@linaro.org wrote: In-order to make reproducible builds we create pinned manifests with each commit explicitly listed. We also use this method to create a release.

Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-12 Thread John Rigby
On Tue, Jul 12, 2011 at 1:07 AM, Ricardo Salveti ricardo.salv...@linaro.org wrote: On Mon, Jul 11, 2011 at 6:18 PM, Alexander Sack a...@linaro.org wrote: On Mon, Jul 11, 2011 at 4:11 PM, Zach Pfeffer zach.pfef...@linaro.org wrote: In-order to make reproducible builds we create pinned

Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-12 Thread John Stultz
On Tue, 2011-07-12 at 04:07 -0300, Ricardo Salveti wrote: On Mon, Jul 11, 2011 at 6:18 PM, Alexander Sack a...@linaro.org wrote: On Mon, Jul 11, 2011 at 4:11 PM, Zach Pfeffer zach.pfef...@linaro.org wrote: In-order to make reproducible builds we create pinned manifests with each commit

Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-12 Thread Zach Pfeffer
It is fragile, but I think its the only way to do it and still give people the ability to create arbitrary builds easily, with 100% fidelity using a method that's easy to automate and that generally works. Since we need to use repo -r, we don't want to have people using side gits if we can help

Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-11 Thread John Stultz
On Mon, 2011-07-11 at 09:11 -0500, Zach Pfeffer wrote: In-order to make reproducible builds we create pinned manifests with each commit explicitly listed. We also use this method to create a release. We depend on these pinned commits - if they don't exist the released builds can no longer be

Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-11 Thread Alexander Sack
On Mon, Jul 11, 2011 at 4:11 PM, Zach Pfeffer zach.pfef...@linaro.org wrote: In-order to make reproducible builds we create pinned manifests with each commit explicitly listed. We also use this method to create a release. We depend on these pinned commits - if they don't exist the released

Re: Please tag commits referred to by pinned and release manifests in Android builds

2011-07-11 Thread Zach Pfeffer
As Alexander says, we need to be able to reference the sha since our pinned-manifest list all the subgit syncables by sha. Like this: https://android-build.linaro.org/jenkins/job/linaro-android_beagle-11.07-release/1/artifact/build/out/pinned-manifest.xml -Zach On 11 July 2011 16:18, Alexander