Draft: Git Migration

[maltejur]

No description provided.

[tomrittervg]

So what's reset_repository for? It doesn't seem to be called by anything?

[maltejur]

So what's reset_repository for? It doesn't seem to be called by anything?

It's used in vendoring.py, it just doesn't show up in the diff because the same function was also used with Mercurial previously.

[tomrittervg]

I don't have any criticisms, it seems fine if it works.

From experience, the situation around reseting the repo for the next project to run gave me many problems, leading me to add "hg status" in various places for debugging. You may consider the same. LMK when it's working and I'll look again and stamp.

[maltejur]

After some further work on this, I think it's best if we just stick to Mercurial for now. For machine-to-machine try pushes, Mercurial is currently still the only supported option (see Bug 1994568). And switching Updatebot to Git now using Cinnabar to push to the Mercurial try server would require numerous changes in the Taskcluster code that would become obsolete the moment Mercurial isn't used anymore for try pushes, i.e., the moment we would actually need to migrate Updatebot to Git.

But for what it's worth, as soon as Bug 1994568 is fixed, this PR can/should be picked up again and should also be mostly ready to go with some minimal changes required in taskcluster/docker/updatebot/run.py in-tree to make sure a Git checkout is used and potential Lando credentials are provided.