Re: [chromium-dev] PSA: sub-tree mirrors of chromium/src.git will be lagged for ~2 hours

25 views
Skip to first unread message

Ryan Sleevi

unread,
Aug 22, 2014, 1:09:09 AM8/22/14
to Robbie Iannucci, James Robinson, Chromium-dev, Chromium OS dev

These were mirrored for ChromeOS, in particular, the deprecated 'platform' work (it has been replaced by 'platform2', which uses GYP and is much more hermetic)

If anything breaks, it should hopefully be constrained only to certain deprecated CrOS workflows.

On Aug 21, 2014 9:57 PM, "Robert Iannucci" <iann...@chromium.org> wrote:
Yes, they're all just directories in the chromium tree, but they're currently mirrored independently on chromium.googlesource.com. This is done today with git-svn, by having it mirror those subdirectories from svn to git. After chromium/src.git is a real git-repo, that will no longer be an option. What I'm doing is setting up a daemon which will mirror from the full src.git repo to these subtree mirrors.

For example, here's the repo mirror of the src/net subdirectory: https://chromium.googlesource.com/chromium/src/net.git

After this change is done, instead of being updated from src.chromium.org/viewvc/chrome/trunk/src/net via git-svn, it will be updated (same content) from src.git via an efficient daemon.

This was done in lieu of hunting down all the consumers of the existing sub-repo mirrors and getting them to change. This way we can transparently continue to provide these subtree mirrors.

Rob




On Thu, Aug 21, 2014 at 9:52 PM, James Robinson <jam...@chromium.org> wrote:



On Thu, Aug 21, 2014 at 7:39 PM, Robert Iannucci <iann...@chromium.org> wrote:
TL;DR: The following git repos will have about 2 hours of lag (on chromium.googlesource.com):
  • chromium/src/base
  • chromium/src/build
  • chromium/src/crypto
  • chromium/src/dbus
  • chromium/src/gpu
  • chromium/src/media
  • chromium/src/mojo
  • chromium/src/net

These (and several few others) are just directories in the chromium tree, not standalone projects.  What do you mean by the git repo?  Are projects pulling these independently?

- James

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

Robert Iannucci

unread,
Aug 22, 2014, 1:10:43 AM8/22/14
to Ryan Sleevi, James Robinson, Chromium-dev, Chromium OS dev
Hopefully :). I didn't want to spend a lot of time hunting for downstream dependencies on these repos, which is usually a endless endeavor. The subtree daemon is only going to push fast-forwards on these repos though, so I'm pretty hopeful that no one will really even notice that it's different.

Robert Iannucci

unread,
Aug 22, 2014, 1:12:31 AM8/22/14
to James Robinson, Ryan Sleevi, Chromium-dev, Chromium OS dev



On Thu, Aug 21, 2014 at 10:11 PM, James Robinson <jam...@chromium.org> wrote:
OK, so this won't impact most chromium developers who are just using src.git.  Thanks for the clarification.

Correct

Robert Iannucci

unread,
Aug 22, 2014, 2:46:20 AM8/22/14
to James Robinson, Ryan Sleevi, Chromium-dev, Chromium OS dev
Forgot to hit send, but this is completed, and you can see a live mirrored commit here: https://chromium.googlesource.com/chromium/src/media/+/58bb04040d462aaa868135abfd4e20b6e9dfec8c

Robert Iannucci

unread,
Aug 22, 2014, 12:54:45 PM8/22/14
to Viet-Trung Luu, Ryan Sleevi, James Robinson, Chromium-dev, Chromium OS dev
Yep, I completely agree, I just wanted to decouple that from the migration. FWIW, the new daemon is substantially less complex than the previous one.

In general, I'm in strong favor of removing code and disabling redundant systems :)


On Fri, Aug 22, 2014 at 8:38 AM, Viet-Trung Luu <viettr...@chromium.org> wrote:
Gah, from the right email address this time.

On Fri, Aug 22, 2014 at 8:37 AM, Viet-Trung Luu <v...@google.com> wrote:
On Thu, Aug 21, 2014 at 10:10 PM, Robert Iannucci <iann...@chromium.org> wrote:
Hopefully :). I didn't want to spend a lot of time hunting for downstream dependencies on these repos, which is usually a endless endeavor. The subtree daemon is only going to push fast-forwards on these repos though, so I'm pretty hopeful that no one will really even notice that it's different.

This seems like a reasonable solution at this moment, but we should try to turn down as many of those mirrors at some point, rather than eternally accumulating maintenance burden.

We should also track down all dependencies, and find a way of tracking new dependencies. (Even a policy saying that any new dependencies should add themselves to a spreadsheet -- or else they'll be broken whenever we feel like it -- would be progress.)
 
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.



Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages