Skip to content

C
Chromium_Depot_tools
Switch branch/tag
  1. 12 Nov, 2015 2 commits
  3. 01 Jun, 2015 1 commit
  5. 26 May, 2015 1 commit
  7. 27 Apr, 2015 1 commit
  9. 17 Feb, 2015 1 commit
    • primiano@chromium.org's avatar
      Reland "Make gclient ready for the Blink (DEPS to main project)" · 1c127389
      primiano@chromium.org authored 
      Reland crrev.com/743083002, which was reverted in crrev.com/796053002
due to some test flakiness, probably related with an old version of Git on
the bots. Relanding now that the infra has been updated to Trusty (plus
adding some de-flake precautions).

Original CL Description:
Make gclient ready for the Blink (DEPS to main project) transition

This CL makes gclient understand correctly whether a git project is
being moved from DEPS to an upper project and vice-versa.
The driving use case for this is the upcoming Blink merge, where
third_party/Webkit will be removed from DEPS (and .gitignore) and will
become part of the main project.

At present state, gclient leaves the .git folder around when a project
is removed from DEPS, and that causes many problems.

Furthermore this CL solves the performance problem of bisecting across
the merge point. The subproject's (Blink) .git/ folder is moved to a
backup location (in the main checkout root) and is restored when moving
backwards, avoiding a re-fetch when bisecting across the merge point.

BUG=431469

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@294082 0039d316-1c4b-4281-b951-d872f2087c98
      1c127389
  11. 11 Dec, 2014 2 commits
  13. 10 Dec, 2014 1 commit
    • primiano@chromium.org's avatar
      Make gclient ready for the Blink (DEPS to main project) transition · fcf03763
      primiano@chromium.org authored 
      This CL makes gclient understand correctly whether a git project is
being moved from DEPS to an upper project and vice-versa.
The driving use case for this is the upcoming Blink merge, where
third_party/Webkit will be removed from DEPS (and .gitignore) and will 
become part of the main project.

At present state, gclient leaves the .git folder around when a project
is removed from DEPS, and that causes many problems. 

Furthermore this CL solves the performance problem of bisecting across
the merge point. The subproject's (Blink) .git/ folder is moved to a
backup location (in the main checkout root) and is restored when moving
backwards, avoiding a re-fetch when bisecting across the merge point. 

BUG=431469

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@293329 0039d316-1c4b-4281-b951-d872f2087c98
      fcf03763
  15. 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
  17. 05 Aug, 2014 2 commits
  19. 02 Jul, 2014 1 commit
  21. 07 May, 2014 1 commit
  23. 09 Apr, 2014 1 commit
  25. 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
  27. 01 Apr, 2014 1 commit
  29. 10 Mar, 2014 2 commits
  31. 26 Feb, 2014 2 commits
  33. 20 Feb, 2014 1 commit
  35. 13 Feb, 2014 2 commits
  37. 11 Feb, 2014 2 commits
  39. 06 Feb, 2014 1 commit
  41. 05 Feb, 2014 1 commit
  43. 17 Jan, 2014 2 commits
  45. 15 Oct, 2013 1 commit
  47. 17 Aug, 2013 1 commit
  49. 20 Jul, 2013 1 commit
  51. 03 Jul, 2013 1 commit
    • iannucci@chromium.org's avatar
      Add a git cache for gclient sync operations. · 53456aa2
      iannucci@chromium.org authored 
      Instead of cloning straight into place, clones are made to a global cache dir,
and then local (using --shared) clones are made from the cache to the final
resting place. This means the 'final' clones are full repos with no shenanigans,
meaning that branches, commits, etc. all work, which should allow the rest of
the gclient ecosystem to work without change as well.

The primary benefit is, of course, reduced network IO, and a much lower cost for
'clobber' operations (assuming we don't clobber the cache). It also means that
a given bot can have a greater number of checkouts, since the entire git history
will only be stored once per machine, instead of once per checkout.

R=dpranke@chromium.org, szager@chromium.org
BUG=

Review URL: https://chromiumcodereview.appspot.com/18328003

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@210024 0039d316-1c4b-4281-b951-d872f2087c98
      53456aa2
  53. 29 May, 2013 1 commit
  55. 18 Apr, 2013 1 commit
  57. 15 Nov, 2012 1 commit
  59. 27 Sep, 2012 1 commit
  61. 02 Mar, 2012 1 commit
  63. 11 Nov, 2011 1 commit