Danek Duvall wrote:
> On Wed, Sep 17, 2008 at 01:44:50PM -0700, Mike Sullivan wrote:
>
>> My concerns are failed builds and now having to coordinate two putbacks
>> (and that not involving me having to wake up at 3am to copy someones tar
>> file :).
>
> We could always require that the RTI not be approved until the tarballs are
> in place. And the tarballs can always be put in place long before the
> putback happens, just to be ready.
true - but that requires the RTI approvers to enforce it which bothers
me a bit, and means that again the person _could_ have putback at 3am
Pacific time but has to wait until the US-approver they picked wakes up.
>
> SMA will still have to keep their tarball in the gate, or give up on their
> craptastic method of updating the tarball in place.
they have actually started patching instead, due to someone, umm,
suggesting future RTIs were going to require that.
> As for potential network outages, we can create a mechanism to pre-download
> the tarballs and point the build at a cache directory instead of
> downloading on each build. That would also allow multiple copies of the
> gate to share the disk space and download time (and cost) associated with
> the tarballs, which is likely a huge win, on the balance, for everyone.
Well my little caching change was dumping them into your workspace but I
suppose you could share them between builds (though probably by
preloading the cache and not by letting builds race through and possibly
break trying to copy in the same files).
> I think getting that working is probably worth pushing out the target
> build, if it can't be done in that time, but that's probably more up to the
> tech lead and whatever steam valve you happen to be facing. :)
I am quite happy to have someone else go off and do it a better way,
I have many bugs I'd like to fix once the gate is actually clean
again and todays randomly required paperwork is finished.
Mike
