1. 06 Feb, 2018 1 commit
  2. 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
  3. 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
  4. 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
  5. 27 May, 2017 1 commit
  6. 10 May, 2017 1 commit
  7. 01 May, 2017 1 commit