Google Git
Sign in
gerrit / git-repo / 355f4398d870573255574c895f808485310b5c10
commit355f4398d870573255574c895f808485310b5c10[log] [tgz]
authorMike Frysinger <vapier@google.com>Wed Jul 20 17:15:29 2022 -0400
committerMike Frysinger <vapier@google.com>Mon Jul 25 15:36:43 2022 +0000
treedcdf96fd22bed67ac5fdf57644d7ad6e7b2a4865
parentbddc964d9340c66066590a81d21934362fb0c490 [diff]
sync: rework --jobs to provide better defaults

For --jobs-network, the logic is now:
* If the user specifies --jobs-network, use that.
* Else, if the user specifies --jobs, use that.
* Else, if the manifest specifies sync-j, use that.
* Else, default to 1.
Then we limit the jobs count based on the softlimit RLIMIT_NOFILE.

For --jobs-checkout, the logic is now:
* If the user specifies --jobs-checkout, use that.
* Else, if the user specifies --jobs, use that.
* Else, if the manifest specifies sync-j, use that.
* Else, default to DEFAULT_LOCAL_JOBS which is based on user's ncpus.
Then we limit the jobs count based on the softlimit RLIMIT_NOFILE.

For garbage collecting, the logic is now:
* If the user specifies --jobs, use that.
* Else, if the manifest specifies sync-j, use that.
* Else, default to the user's ncpus.
Then we limit the jobs count based on the softlimit RLIMIT_NOFILE.

Having to factor in the manifest settings makes this more complicated
which is why we delay processing of defaults until after we've synced
the manifest projects.

Bug: http://b/239712300
Change-Id: Id27cda63c76c156f1d63f6a20cb2c4ceeb3d547c
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/341394
Tested-by: Mike Frysinger <vapier@google.com>
Reviewed-by: LaMont Jones <lamontjones@google.com>
2 files changed
tree: dcdf96fd22bed67ac5fdf57644d7ad6e7b2a4865
  1. .github/
  2. docs/
  3. hooks/
  4. man/
  5. release/
  6. subcmds/
  7. tests/
  8. .flake8
  9. .gitattributes
  10. .gitignore
  11. .gitreview
  12. .mailmap
  13. .project
  14. .pydevproject
  15. color.py
  16. command.py
  17. completion.bash
  18. editor.py
  19. error.py
  20. event_log.py
  21. fetch.py
  22. git_command.py
  23. git_config.py
  24. git_refs.py
  25. git_ssh
  26. git_superproject.py
  27. git_trace2_event_log.py
  28. gitc_utils.py
  29. hooks.py
  30. LICENSE
  31. main.py
  32. MANIFEST.in
  33. manifest_xml.py
  34. pager.py
  35. platform_utils.py
  36. platform_utils_win32.py
  37. progress.py
  38. project.py
  39. README.md
  40. repo
  41. repo_trace.py
  42. requirements.json
  43. run_tests
  44. setup.py
  45. ssh.py
  46. SUBMITTING_PATCHES.md
  47. tox.ini
  48. wrapper.py
README.md

repo

Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.

Contact

Please use the repo-discuss mailing list or issue tracker for questions.

You can file a new bug report under the “repo” component.

Please do not e-mail individual developers for support. They do not have the bandwidth for it, and often times questions have already been asked on repo-discuss or bugs posted to the issue tracker. So please search those sites first.

Install

Many distros include repo, so you might be able to install from there.

# Debian/Ubuntu.
$ sudo apt-get install repo

# Gentoo.
$ sudo emerge dev-vcs/repo

You can install it manually as well as it's a single script.

$ mkdir -p ~/.bin
$ PATH="${HOME}/.bin:${PATH}"
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
$ chmod a+rx ~/.bin/repo