Upsouce takes 6 to 10 minutes to synchronize the latest git commit, when the git repo is relatively large.
Upsouce takes 6 to 10 minutes to synchronize the latest git commit, when the git repo is relatively large.
Is there any configuration that can limit the synchronization scope of git repository?
For example, synchronization of tags is not allowed, but only specified branches are allowed to be synchronized?
Or are there other tuning parameters?
publish.git info
54,029 Commits
443 Branches
1,527 Tags
2.2 GB Files
2.2 GB Storage
hardware:
16C 64G
logs
root@upsource-server-Debian-14:/data/Upsource/upsource-3.5.3597/logs/upsource-frontend# grep publish all.log|grep VcsService-11|grep -v wangxn-xxgroup
[2024-04-01 15:55:06,515] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: started
[2024-04-01 15:55:06,515] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: Fetching repository...
[2024-04-01 15:58:29,367] INFO VcsService-11 xproject1203 ggers.vcs.git.FetchCommandImpl - Git fetch finished for: git@gitlab.rd.xx.com:xxgroup/publish.git in directory: /data/Upsource/upsource-3.5.3597/temp/upsource-frontend/vcs-service/caches/plugins/git/git-E4D2B17B.git, took 2378ms
[2024-04-01 15:58:29,725] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: Loading commits graph...
[2024-04-01 16:01:14,522] INFO VcsService-11 xproject1203 ing.MappingCommitsGraphBuilder - [xproject1203:publish] Constructed graph
[2024-04-01 16:01:14,522] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: finished
[2024-04-01 16:16:48,750] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: started
[2024-04-01 16:16:48,750] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: Fetching repository...
[2024-04-01 16:16:54,454] INFO VcsService-11 xproject1203 ggers.vcs.git.FetchCommandImpl - Git fetch finished for: git@gitlab.rd.xx.com:xxgroup/publish.git in directory: /data/Upsource/upsource-3.5.3597/temp/upsource-frontend/vcs-service/caches/plugins/git/git-E4D2B17B.git, took 2440ms
[2024-04-01 16:16:54,801] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: Loading commits graph...
[2024-04-01 16:16:54,805] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: finished
[2024-04-01 17:28:11,664] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: started
[2024-04-01 17:28:11,665] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: Fetching repository...
[2024-04-01 17:29:15,096] INFO VcsService-11 xproject1203 ggers.vcs.git.FetchCommandImpl - Git fetch finished for: git@gitlab.rd.xx.com:xxgroup/publish.git in directory: /data/Upsource/upsource-3.5.3597/temp/upsource-frontend/vcs-service/caches/plugins/git/git-E4D2B17B.git, took 2409ms
[2024-04-01 17:29:15,453] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: Loading commits graph...
[2024-04-01 17:32:31,851] INFO VcsService-11 xproject1203 ing.MappingCommitsGraphBuilder - [xproject1203:publish] Constructed graph
[2024-04-01 17:32:31,852] INFO VcsService-11 xproject1203 ce.LoggingFetchServiceCallback - Fetching xproject1203/publish: finished
Please sign in to leave a comment.
update to the Build 2020.1.1992 fixed this problem.
Got some new problems:
1. when I search {this year} created review, the review created at last year are in the list. ( updated at was changed)
2. sometimes some branch has new commit after created, but upsource return “The branch appears to be empty”
this project doesn't set default branch.
Upsource get compare branch, compare two branches, have 2 commit and 1 filediff.