> > 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.
> >
> I don't really like separating the tarballs from the gate and I don't
> think that forcing tarball integration prior to RTI approval solves all
> of the problems. If hg is capable of it (and I haven't looked into it
> enough), we can add hooks to force the upload of missing tarballs at
> commit (push) time
That is possible, but the source files can be quite big and it might
take long to download them from internet. More doable seems to be to
have check that the files are already in place, rejecting the push if it
is not the case. I'll investigate how possible that would be.
> and download of tarballs when a workspace is cloned or pulled.
That would be possible, but maybe unnecessary complex if every
application/product would have simple way of getting it's sources, and
if there would be simple way of getting all sources.
> > 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.
> >
> See above, but this should happen as part of the workspace clone or
> update process, possibly via hg hooks.We can definitely do this via a
> build target, but it would be better if we could do this through hg
> hooks. That way it would happen as part of the workspace clone or update
> process.
Well, if there's simple way to get all necessary sources, one can
install his own hook to do exactly that.
> Are there any mercurial experts here that want to step up to help solve
> this? provide assistence? , ...
I am interested in seeing what happens if you block for a while on
server side during push. But I guess that means that the gate is locked
for another push, if not even for pull. I can whip some examples to have
something to start with.
--
Vlad
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 193 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/sfwnv-discuss/attachments/20080918/e728bb72/attachment.bin>
