Currently repo repos are synced via prod push or devserver push.  I would like to avoid the case of some of our machines syncing repo repos via prod push and some of our machines syncing repo repos via Puppet.

I support making all repo repos be synced via Puppet, but that requires some planning.  Puppet would always sync to a stable branch, and prod push will uprev the stable branch and force Puppet runs instead of the repo syncs it runs now.

Someone needs to acquire the knowledge for how to make new repo branchs and how repo tracks branchs and the manifest format for that.

Is this work urgent? Or is this a fixit candidate for future?

This is not urgent, but as long as this is not fixed certain repos in prod are getting stale (need to be sync'ed by hand from time to time). These repos are not critical (yet).

It is a fixit candidate with a caveat -- we need to sit down and decide before a Fixit what we want to do here. The actual implementation is Fixit sized, but the decision needs some more thought.

This also broke sysmon on some servers. (at least most of the devservers, don't know what else).
See issue 723367 and  issue 723493 .

I think we need an interim solution to this problem, maybe just to sync the ~/chromiumos repo which is not maintained by anything at all currently.

chromiumos repo should be synced by prod push

https://cs.corp.google.com/android/external/autotest/site_utils/deploy_server_local.py?q=_sync_chromiumos_repo&l=467

Needs some design before fixit

This bug is very old, is Untriaged, and has no owner.  If it is still relevant, reopen as Untriaged or open a new bug