On 1 July 2011 03:00, Eliot Miranda <
[hidden email]> wrote:
>
>
>
> On Thu, Jun 30, 2011 at 3:28 PM, Igor Stasenko <
[hidden email]> wrote:
>>
>> I am thinking, how is better to track Hudson builds.
>> Currently VM reports a build by taking a VMMaker package version.
>> But it is incomplete information:
>> - there is no evidence which sources been used and which
>> configuration of CMakeVMMaker been used.
>>
>> Hudson fetching everything from git, so using git hash number is a
>> complete pointer to the sources.
>> But in addition, i need to specify which configuration been used
>> (since there are many of them).
>> Actually i think that the more information we put, the easier it would
>> be to track down, which VM are used.
>>
>> So, my question, what is your preferences?
>> Because currently 'Cog 4.0.0' as well as 'VMMaker-foo-bar.xyz' says
>> almost nothing :)
>
> VMMaker-foo-bar.xyz says /everything/ about the source covered by VMMaker.
But it says nothing what configuration used to build. Given same
sources you can produce multiple VMs.
> I want the Monticello package lists for all packages involved (there's OSProcessPlugin and some others outside of VMMaker). I want the url of the platforms tree and the revision (i.e. the exact coordinate to check-out the exact same source).
Yes.. need to think about it.
> This is all about reproducibility. You provide exact coordinates. From those coordinates anyone can recreate the source. That's why I check-in the generated source along with the platforms and build trees. That way one only has to dereference a single coordinate, the svn tree.
And that's why i checking in not all sources but just an script which
required to reproduce image with VMMaker.
--
Best regards,
Igor Stasenko AKA sig.
Locked
