1. 07 Sep, 2017 2 commits
  2. 02 Aug, 2017 1 commit
  3. 28 Jul, 2017 1 commit
    • Dan Jacques's avatar
      [bootstraps] Sync at gclient, suppress output (#2) · 5aeeb72c
      Dan Jacques authored
      Have the "update_depot_tools" script also do a CIPD tool sync. This will
      ensure that users and systems have access to tooling at sync-time rather
      than just-in-time loading them at execution time.
      
      Update the tool boostraps to suppress any sort of syncing logs, if it
      does happen. This will ensure that users who execute the tools don't see
      unexpected output.
      
      BUG=chromium:748651
      TEST=local
        - Tested on Mac and Windows.
      
      Change-Id: I1aad897d885a07beeac40a372a658681720efd2a
      Reviewed-on: https://chromium-review.googlesource.com/591229
      Commit-Queue: Daniel Jacques <dnj@chromium.org>
      Reviewed-by: 's avatarRobbie Iannucci <iannucci@chromium.org>
      5aeeb72c
  4. 26 Jul, 2017 1 commit
    • Dirk Pranke's avatar
      Revert "[bootstraps] Sync at gclient, suppress output." · 44855b94
      Dirk Pranke authored
      This reverts commit 4d92fe43.
      
      Reason for revert: This moved the logging from invoking `led` or `vpython` to whenever someone would run something that would end up invoking `update_depot_tools`. It's good that we are calling this when we run update_depot_tools, but we probably should've suppressed the logging there in at least the success case, because now things are even more confusing. See crbug.com/748651.
      
      Original change's description:
      > [bootstraps] Sync at gclient, suppress output.
      > 
      > Have the "update_depot_tools" script also do a CIPD tool sync. This will
      > ensure that users and systems have access to tooling at sync-time rather
      > than just-in-time loading them at execution time.
      > 
      > Update the tool boostraps to suppress any sort of syncing logic, if it
      > does happen. This will ensure that users who execute the tools don't se
      > unexpected output.
      > 
      > BUG=None
      > TEST=local
      >   - Tested on Mac and Windows.
      > 
      > R=​dpranke@chromium.org, iannucci@chromium.org
      > 
      > Change-Id: I8efce8c73cc4e82ffdf5067ba9b917119a81e843
      > Reviewed-on: https://chromium-review.googlesource.com/581494
      > Commit-Queue: Daniel Jacques <dnj@chromium.org>
      > Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
      
      TBR=iannucci@chromium.org,dpranke@chromium.org,dnj@chromium.org
      
      # Not skipping CQ checks because original CL landed > 1 day ago.
      
      Bug: None
      Change-Id: I2485c9dd2e48a8dbdeebfff5da9d4c708e0edcb7
      Reviewed-on: https://chromium-review.googlesource.com/585867Reviewed-by: 's avatarDirk Pranke <dpranke@chromium.org>
      Commit-Queue: Dirk Pranke <dpranke@chromium.org>
      44855b94
  5. 24 Jul, 2017 1 commit
    • Dan Jacques's avatar
      [bootstraps] Sync at gclient, suppress output. · 4d92fe43
      Dan Jacques authored
      Have the "update_depot_tools" script also do a CIPD tool sync. This will
      ensure that users and systems have access to tooling at sync-time rather
      than just-in-time loading them at execution time.
      
      Update the tool boostraps to suppress any sort of syncing logic, if it
      does happen. This will ensure that users who execute the tools don't se
      unexpected output.
      
      BUG=None
      TEST=local
        - Tested on Mac and Windows.
      
      R=dpranke@chromium.org, iannucci@chromium.org
      
      Change-Id: I8efce8c73cc4e82ffdf5067ba9b917119a81e843
      Reviewed-on: https://chromium-review.googlesource.com/581494
      Commit-Queue: Daniel Jacques <dnj@chromium.org>
      Reviewed-by: 's avatarRobbie Iannucci <iannucci@chromium.org>
      4d92fe43
  6. 07 Jul, 2017 1 commit
  7. 01 Jun, 2017 1 commit
  8. 21 Jun, 2016 1 commit
  9. 23 May, 2016 1 commit
  10. 04 Apr, 2016 1 commit
  11. 30 Mar, 2016 2 commits
  12. 09 Nov, 2015 3 commits
  13. 11 Sep, 2015 1 commit
  14. 29 Jun, 2015 1 commit
  15. 25 Jun, 2015 1 commit
  16. 24 Jun, 2015 2 commits
  17. 13 Apr, 2015 1 commit
  18. 12 Dec, 2014 1 commit
  19. 10 Dec, 2014 1 commit
  20. 25 Nov, 2014 1 commit
  21. 19 Mar, 2014 1 commit
  22. 21 Feb, 2014 1 commit
  23. 18 Jan, 2014 1 commit
  24. 16 Jan, 2014 2 commits
  25. 08 Oct, 2013 1 commit
  26. 23 Jan, 2013 1 commit
  27. 07 Jan, 2013 1 commit
  28. 03 Jan, 2013 1 commit
  29. 26 Nov, 2012 1 commit
  30. 09 Nov, 2012 1 commit
  31. 17 Jul, 2012 1 commit
  32. 01 May, 2012 1 commit
    • cmp@chromium.org's avatar
      Handle updating depot_tools repos that are git cloned. · b9d08cec
      cmp@chromium.org authored
      Until recently, no proper Git clone of depot_tools existed.
      All Git clones were set up locally via git svn clone.  The
      way repos of that type are updated is via 'git svn rebase'.
      
      Now, a supported Git clone of depot_tools exists.  The
      update process for repos of this type is via 'git fetch'
      and 'git rebase'.
      
      Modify the update_depot_tools* scripts so they can update
      depot_tools for git cloned or git svn cloned methods.  This
      also means that git svn is no longer required, so move that
      test after we check for git cloned repos.
      
      R=maruel@chromium.org
      
      TEST=Linux + git clone: on Linux, git clone
      https://git.chromium.org/chromium/tools/depot_tools.git.  Apply
      and commit this patch locally.  Note commit hash of HEAD.  Run
      'git reset --hard "HEAD^^^"'.  Run
      'git cherry-pick HASH_OF_UPDATE_CHANGE'.  Run './update_depot_tools'.
      Verify depot_tools is updated to latest available revision + this
      change.
      
      TEST=Linux + git svn clone: on Linux, git svn clone
      svn://svn.chromium.org/chrome/trunk/tools/depot_tools.
      Apply and commit this patch locally.  Note commit hash
      of HEAD.  Run 'git reset --hard "HEAD^^^"'.  Run 'git cherry-pick
      HASH_OF_UPDATE_CHANGE'.  Run './update_depot_tools'.  Verify
      depot_tools is updated to latest available revision + this change.
      
      TEST=Windows command prompt + git clone: on Windows command prompt,
      run Linux+git clone test, except use update_depot_tools.bat.  Verify
      depot_tools is updated to latest available revision + this change.
      
      TEST=Windows command prompt + git svn clone: on Windows command
      prompt, run Linux+git svn clone test, except use
      update_depot_tools.bat.  Verify depot_tools is updated to latest
      available revision + this change.
      
      TEST=Windows cygwin + git clone: on Windows command prompt,
      run Linux+git clone test.  Verify depot_tools is updated to latest
      available revision + this change.
      
      TEST=Windows cygwin + git svn clone: on Windows command
      prompt, run Linux+git svn clone test.  Verify depot_tools is updated
      to latest available revision + this change.
      
      Review URL: https://chromiumcodereview.appspot.com/10263004
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@134732 0039d316-1c4b-4281-b951-d872f2087c98
      b9d08cec
  33. 13 Apr, 2012 1 commit
  34. 29 Sep, 2011 1 commit