sameersbn / sameersbn/docker-gitlab
Build failed GITLAB-CI cloning large repository
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
In Giltlab-ci when cloning project with large repository , build failed after 5mins.
No issue with smaller repository
No issue to clone repository from git
Using container docker-gitlab:9.1.2
Any idea how to fix it ?
Running with gitlab-ci-multi-runner 9.1.0 (0118d89)
on ED-CZC90190MC_BASH (eeb51f85)
Using Shell executor...
Running on ED-CZC90190MC...
Cloning repository...
Clonage dans '/home/frebour1/build/builds/eeb51f85/0/frebour1/project_x'...
**error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 Gateway Time-out
fatal: The remote end hung up unexpectedly**
ERROR: Job failed: exit status 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the GitLab CI cloning log and the docker-gitlab:9.1.2 setup, focusing on the HTTP 504 and five-minute failure for large repositories. Reproduce the clone with a large repository and compare it with a smaller one; done means the large repository clones successfully without the job failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, shell
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100