Repository mirroring: Support for configurable sync time
- Zendesk ticket: https://gitlab.zendesk.com/agent/tickets/13079
- Dev link: None
- GitLab version: 8.2
Customer would like support for a configurable mirror sync interval. They feel one hour is not sufficient in their case.
@DouweM @dzaporozhets What do you think?
Activity
mentioned in merge request !51 (merged)
@DouweM Their use-case is trying to keep in sync with their company's upstream git server. Not sure if that's a use-case we want to solve for.
This got me thinking - how are we currently keeping our GitHub repo synced in both directions?
@dblessing We push and pull from GitHub manually every so often.
As you're aware, Repository Mirroring currently only does pull sync, not push. Do they intend to work in both repositories? That's not going to work, and will always be a hard problem to solve.
@dblessing I'm okay with a different sync schedule. How often would they like to sync?
@DouweM Probably every 5 minutes or some really short interval. Are you proposing to make it configurable or change the default?
@dblessing I'm mostly afraid of the effect on load when people start adding mirror repositories to GitLab.com and we're refreshing hundreds of them every five minutes. Even if we don't make it a default, lots of people will choose that option.
cc @dzaporozhets What do you think?
@dblessing @DouweM Frequent sync should not be that big problem since the more often you do pull/fetch - the less new data will be downloaded. Agree that we should not allow really small interval. Few options for different kind of workflow should be enough. For example:
- every 15 minutes
- every hour (default)
- once a day
@dzaporozhets All right, makes sense.
@JobV Can you please schedule?
mentioned in commit 61c651d7
Added promised label
Reassigned to @rspeicher
Milestone changed to 8.7
mentioned in merge request !299 (closed)
Milestone changed to 8.8
Milestone changed to %8.9
@rspeicher this is assigned to you, can you give it a weight of work left?
Milestone changed to %8.10
@JobV Done, but unassigning myself for now in the hopes that someone else can pick it up.
Milestone changed to %8.11
mentioned in merge request !608 (merged)
Milestone changed to %8.12
Here's our use case - we want to try Gitlab CI, but do not want/can (yet) migrate to GitLab for git. In order for builds to be triggered in a timely manner, the repo sync should happen pretty often. 5 minutes would be OK, every minute or even 30 seconds would be ideal.
Some other options I can think of:
- is there a way to notify GitLab when there is a change in the upstream repo (Bitbucket or Github)?
- is there a way to use GitLab CI directly and trigger builds from the upstream repo (Bitbucket or Github)?
Milestone changed to %8.13
Milestone changed to %8.14
Mentioned in commit 61c651d7
Milestone changed to %8.15
changed milestone to %8.16
added Deliverable label
mentioned in issue #98 (closed)
changed milestone to %8.17
assigned to @tiagonbotelho
mentioned in merge request !1115 (merged)
Are we supposed to set sync times only for pull or for push aswell? \cc @dblessing @DouweM @dzaporozhets
closed via merge request !1115 (merged)
Here is our use case:
Github/GitLab/Gerrit -> Intermediate GitLab gateway -> Enclave GitLab (secure environment) -> Intermediate GitLab gateway -> Github/GitLab/Gerrit
The developers can't pull/push to the intermediate server from within the enclave. So the intermediate gateway does the job of pushing/pulling.
And the cycle starts all over again. The enclave is quite often in some other country.
The number of hops times the interval of syncing adds up to a lengthy delay. I think 15 minutes is too long, but bearable. Productivity tends to suffer somewhat. In our case, it would be ideal to have events trigger the sync.
mentioned in merge request !2366 (merged)
mentioned in commit 3d21ace0
