-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.20.22, 9.4.6, 9.8.1
-
8.2
-
12
-
Severity 3 - Minor
-
2
-
Issue Summary
This is reproducible on Data Center: YES
Steps to Reproduce
- Create organisation in Gitlab (cloud/selfmanaged)
- Generate large repository ~ 100 branches * 100 commits on each branch
- In case of Gitlab self managed -> turn on rate limitation in Administrator panel
- Run Jira (In example 9.8.1 version)
- Create OAuth configuration for Jira <-> Gitlab
- Connect Jira via DVCS connector with Gitlab
- Wait for linking to finish process
- Run Full-Sync in DVCS for linked large repository
- Wait for synchronisation being finished
Expected Results
Synchronisation should work smoothly, or with some pause periods when Gitlab inform us with HTTP 429 about exceeding ratio limit.
Actual Results
DVCS doesn't respect/react on Retry-After header returned by gitlab, and keep asking instance for other changes. In effect DVCS makes unneeded HTTP traffic and populate log files with stack traces containing:
Synchronization failed: Could not get changeset [commitSha] from https://gitlab.com/{further_url}
Workaround
One very inconvenient workaround is to link repositories one by one in DVCS UI panel and reduce simultaneously Git calls
- links to
- mentioned in
-
Page Loading...