|Re: [eclipselink-dev] Github mirroring of eclipselink.runtime broken?|
We've been noticing some funky behaviour from the GitHub mirrors. We
have noticed, for example, that very often the Git repository itself
is up-to-date (within about 15 minutes), but the website reports
very old information.|
Unfortunately, there's nothing that we can do directly. I have been in contact with people at GitHub (and so have others at Eclipse) and it seems that their support for mirrors has some (apparently significant) holes.
I am very close to completely dismantling our automatic support for GitHub mirrors. I have a bug open for this [1,2].
One of the things that we're trying (based on a suggestion from Kevin at GitHub) is to create our own clones under the Eclipse organization banner and manage the pushes to these clones ourselves. Doing it this way gives the project absolute control over how up-to-date the repository is.
The wrinkle is that we (the Eclipse Foundation) can't do this automatically. I can help set up the configuration on the GitHub side of things, but actually cloning the repository and keeping it up-to-date would be the responsibility of the project.
This is a new idea that we're experimenting with. Let me know if you're interested in pursuing this option.
On 03/20/2013 05:04 AM, Heider, Sabine wrote:
Back to the top