how is this being mirrored?

[mattip]

I am a PyPy dev, and am considering how we can use some of the nice CI providers available to github projects but not available to other code hosting sites like foss.heptapod.net

I am curious how you are mirroring this. Is there a machine running a cron job somewhere? Would it be reasonable to mirror via a github actions cron task?

[mozillazg]

@mattip Sorry for my late reply.

I am curious how you are mirroring this

I mirrored this via a fork version of https://github.com/fingolfin/git-remote-hg

Is there a machine running a cron job somewhere?

Yes. I run a job via crontab on my vps.

Would it be reasonable to mirror via a github actions cron task?

Yes, it's possible. Looks like I should merge to use github action instead of crontab, I'll try it later.

[mattip]

I think the version at https://github.com/mnauw/git-remote-hg works better

[mozillazg]

@mattip Thanks for your share, I'll try it when I start to merge the job.

[mozillazg]

@mattip Just create a demo for mirror hg repo with github action ( via https://github.com/mozillazg/git-remote-hg ) and it works:

https://github.com/mozillazg/test-hg-mirror-with-gh-action

This repo will mirror https://foss.heptapod.net/pypy/buildbot to https://github.com/mozillazg/pypy-buildbot

BTW, I am not trying https://github.com/mnauw/git-remote-hg yet, looks like it's more powerful.

[mozillazg]

I mirrored this via a fork version of fingolfin/git-remote-hg

Sorry for this message, I misremembered. In fact, I used a fork version of https://github.com/felipec/git-remote-hg, I have pushed the modified codes from my vps to https://github.com/mozillazg/git-remote-hg

[mattip]

Wow, thanks! What will happen the next time it runs, will it recreate the repo all over again or will it only pick up the changes?

[mozillazg]

It'll recreate the repo all over again, but git push will only push the changes.

[mgorny]

@mozillazg, have you made any progress wrt updating the automation for this repo? We find it very helpful for PyPy packaging on Gentoo but the mirroring delays are a bit of a problem.

Right now I see that default branch has been synced but the release branches or tags haven't.

[mozillazg]

@mgorny Thank you for your feedback. I haven't made any changes to the automated synchronization process recently, so it seems there might be an issue somewhere that has prevented the latest tags from being synced. I will fix it as soon as possible.

[mozillazg]

Right now I see that default branch has been synced but the release branches or tags haven't.

@mgorny The issue has been resolved.

[mgorny]

Right now I see that default branch has been synced but the release branches or tags haven't.

@mgorny The issue has been resolved.

Thanks. Unfortunately, release-pypy2.7-v7.3.12rc1 still isn't there, and release-pypy2.7-v7.x branch seems outdated.

[mozillazg]

Unfortunately, release-pypy2.7-v7.3.12rc1 still isn't there, and release-pypy2.7-v7.x branch seems outdated.

@mgorny Thank you for the reminder. After checking, I found that the reason these two branches were not synchronized is that there is a case in the data of these two branches that the git-remote-hg script I used cannot handle. I plan to try switching to https://github.com/mnauw/git-remote-hg.

[mozillazg]

@mgorny

Unfortunately, release-pypy2.7-v7.3.12rc1 still isn't there, and release-pypy2.7-v7.x branch seems outdated.

The issue has been resolved. Please check again.

• https://github.com/mozillazg/pypy/tree/release-pypy2.7-v7.3.12rc1
• https://github.com/mozillazg/pypy/tree/release-pypy2.7-v7.x

[mattip]

Thanks! Did you use https://github.com/mnauw/git-remote-hg as-is or did you need to modify it?