Skip to content

C
Chromium_Depot_tools
Switch branch/tag
  1. 20 Oct, 2017 1 commit
  3. 19 Oct, 2017 2 commits
  5. 09 Oct, 2017 1 commit
  7. 16 Aug, 2017 1 commit
  9. 14 Jun, 2017 1 commit
  11. 12 Jun, 2017 1 commit
  13. 23 May, 2017 3 commits
  15. 21 Jan, 2017 1 commit
    • Andrii Shyshkalov's avatar
      Fix git cl on windows for git-numberer repos. · 351c61da
      Andrii Shyshkalov authored 
      Git cl decides if git-numberer is enabled on a repository by writing
Gerrit's project.config from refs/meta/config into a tempfile, which is
then queried using `git config -f tempfile --get ...`.  The file itself
is only flushed, but not closed after writing because Python's
tempfile.NamedTemporaryFile is deleted on closing. This worked fine on
Linix/Mac, but not on Windows, where `git config` apparently doesn't see
file or its contents.

This CL rewrites the above using yet another contexmanager temp
directory into which a file is written and closed before git config is
ran.

R=machenbach@chromium.org,grt@chromium.org
BUG=683202

Change-Id: I7974d66b1b2b0478ab4b6f7ac04e547a4981c46c
Reviewed-on: https://chromium-review.googlesource.com/430719
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: 's avatarVadim Shtayura <vadimsh@chromium.org>
      351c61da
  17. 16 Dec, 2016 1 commit
  19. 20 Oct, 2016 1 commit
  21. 11 Oct, 2016 2 commits
  23. 30 Aug, 2016 1 commit
  25. 25 Aug, 2016 1 commit
  27. 24 Aug, 2016 1 commit
  29. 09 Aug, 2016 1 commit
  31. 08 Jun, 2016 1 commit
    • hinoka's avatar
      Add resource locking in gclient · 885e5b1e
      hinoka authored 
      There are entries in the DEPS file where two folders uses the same
git URL (ie. freetype2).  This doesn't work well with git caches because
each task will run on it's own and might try to clobber on top of each other.

This adds another field in a WorkItem which is a list of resources.  When the
work queue is flushed, it has to make sure that none of a newly added workitem
has any resource conflicts.

BUG=618124

Review-Url: https://codereview.chromium.org/2049583003
      885e5b1e
  33. 20 Apr, 2016 1 commit
  35. 05 Jun, 2015 1 commit
  37. 03 Jun, 2015 1 commit
  39. 20 Apr, 2015 1 commit
  41. 23 Feb, 2015 1 commit
  43. 07 Jan, 2015 1 commit
  45. 25 Dec, 2014 1 commit
  47. 12 Nov, 2014 1 commit
  49. 05 Sep, 2014 1 commit
  51. 13 Aug, 2014 1 commit
  53. 06 Aug, 2014 1 commit
    • primiano@chromium.org's avatar
      Reland: Add --no-history option to fetch and gclient for shallow clones. · 5439ea59
      primiano@chromium.org authored 
      Original CL: https://codereview.chromium.org/440263002/

Many people* have complained on chromium-dev about the long times
required to perform a full fetch over a DSL. This seems to be mostly
due to the huge size of chromium's history (~9 GB). On the other side,
not everybody is interested in downloading the full git history of
the projects. The size of git packs required to fetch a working HEAD
is one order of magnitude smaller (1.5 GB).
This change makes it possible to perform a shallow fetch (in a way
which is consistent with DEPS, leveraging git templates on clone),
reducing fetch times by 80% for those not interested in the history.

* See:
[chromium-dev] "fetch chromium" keeps hanging/getting stuck on Windows 7
[chromium-dev] Initial checkout with git taking long
[chromium-dev] Trying to get latest source code fails when fetching
[chromium-dev] Gclient sync takes too long

BUG=228996
TBR=iannucci@chromium.org,szager@chromium.org,wtc@chromium.org

Review URL: https://codereview.chromium.org/440273002

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@287793 0039d316-1c4b-4281-b951-d872f2087c98
      5439ea59
  55. 05 Aug, 2014 2 commits
  57. 25 Jul, 2014 1 commit
  59. 02 Jul, 2014 1 commit
  61. 23 Jun, 2014 1 commit
  63. 25 Apr, 2014 1 commit
  65. 11 Apr, 2014 1 commit
  67. 09 Apr, 2014 1 commit
  69. 08 Apr, 2014 1 commit
    • szager@chromium.org's avatar
      Revamped terminal output for update. · fe0d1902
      szager@chromium.org authored 
      Features:

- Non-verbose output is now limited to a one-line progress
indicator.

- Verbose output is now collated per subprocess.  As soon as a
subprocess finishes, its full output is dumped to terminal.

- Verbose output is prefixed with timestamps representing elapsed
time since the beginning of the gclient invocation.

- git progress indicators ("Receiving objects", etc.) are limited to
one line every 10 seconds.

- In both verbose and non-verbose mode, if a failure occurs, the
full output of the failed update operation is dumped to terminal
just before exit.

- In the event that updates are progressing, but slowly,
"Still working" messages will be printed periodically, to pacify
users and buildbots.

BUG=
R=hinoka@google.com

Review URL: https://codereview.chromium.org/227163002

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@262500 0039d316-1c4b-4281-b951-d872f2087c98
      fe0d1902