sameersbn / sameersbn/docker-gitlab
lag while pulling
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi ,
I have written small script if the commit is done from gitlab webUI.
For example there is one project with multiple directories and some thousands of files, I modified the file and did commit so the commit will call t he custom hooks. So the changes should done automatically in my gitlab server.
This is the script, its very small one.
!/bin/bash
echo "script executed" >> /tmp/gitlog
cd /opt/git/GIT_ROOT/TOOLS_GIT && git pull origin master >> /tmp/gitlog 2> /tmp/error
echo "script execution done" >> /tmp/gitlog
But it is taking lot of time to pull, due to that I am getting 502 error.
I have enabled housekeeping, But I am not sure how to fix it. Can anyone please help me how to increase the performance if the commit is done within seconds modification of file should be done.
Thanks,
Pradeep
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 supplied shell script, especially the git pull command, and inspect the /tmp/gitlog and /tmp/error outputs. Review how the GitLab web UI commit triggers the custom hook and how housekeeping is configured. Done means identifying the cause of the slow pull and verifying that the resulting update completes without a 502 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, gitlab, shell
- Domain
- devops, infrastructure, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100