1. 09 Aug, 2017 9 commits
  2. 08 Aug, 2017 4 commits
  3. 07 Aug, 2017 2 commits
  4. 04 Aug, 2017 2 commits
  5. 03 Aug, 2017 2 commits
  6. 02 Aug, 2017 4 commits
  7. 01 Aug, 2017 3 commits
  8. 31 Jul, 2017 2 commits
  9. 28 Jul, 2017 2 commits
    • 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
    • Dan Jacques's avatar
      [cipd] Bump version, log at warning (#2). · eb1feb90
      Dan Jacques authored
      Bump the CIPD client version to
      b482bfa19d3fa79b4b40dd5ac7a34479052e3df1. This version inculdes support
      for the "-log-level" flag.
      
      Update CIPD bootstrap scripts and tool installation scripts to log at
      warning level, so that standard operation doesn't produce any logs.
      
      This version differs from the previous CL in that the "selfupdate"
      command no longer uses "-log-level". This fixes an issue where the
      current CIPD, which doesn't support "-log-level", is given the flag
      prior to actually updating to a version that does.
      
      BUG=chromium:748651
      TEST=canary
        - Tested this CIPD version on canary waterfall successfully.
      
      Change-Id: I69dfe522d890eb307214f18d0467ce921a766446
      Reviewed-on: https://chromium-review.googlesource.com/589568
      Commit-Queue: Daniel Jacques <dnj@chromium.org>
      Reviewed-by: 's avatarRobbie Iannucci <iannucci@chromium.org>
      eb1feb90
  10. 27 Jul, 2017 3 commits
    • Daniel Jacques's avatar
      Revert "[cipd] Bump version, log at warning." · 9f9d82ac
      Daniel Jacques authored
      This reverts commit 18aa2d93.
      
      Reason for revert: <INSERT REASONING HERE>
      
      Original change's description:
      > [cipd] Bump version, log at warning.
      > 
      > Bump the CIPD client version to
      > e2a98b41adb3403b5b7771c4101b42a55dc2dd9e. This version inculdes support
      > for the "-log-level" flag.
      > 
      > Update CIPD bootstrap scripts and tool installation scripts to log at
      > warning level, so that standard operation doesn't produce any logs.
      > 
      > BUG=chromium:748651
      > TEST=canary
      >   - Tested this CIPD version on canary waterfall successfully.
      >   - Tested "gclient" bootstrap and "vpython" / "led" on Windows system,
      >     no output and works.
      >   - Tested "vpython" / "led" on OSX system, no output and works.
      > 
      > Change-Id: Iae316908283c43c504f293aafdf897df83dccf8d
      > Reviewed-on: https://chromium-review.googlesource.com/588889
      > Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
      > Commit-Queue: Daniel Jacques <dnj@chromium.org>
      
      TBR=iannucci@chromium.org,dnj@chromium.org
      
      Change-Id: Ia611c1aeb204c609ff3469076b8256c54e702230
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: chromium:748651
      Reviewed-on: https://chromium-review.googlesource.com/589527Reviewed-by: 's avatarDaniel Jacques <dnj@chromium.org>
      Commit-Queue: Daniel Jacques <dnj@chromium.org>
      9f9d82ac
    • Dan Jacques's avatar
      [cipd] Bump version, log at warning. · 18aa2d93
      Dan Jacques authored
      Bump the CIPD client version to
      e2a98b41adb3403b5b7771c4101b42a55dc2dd9e. This version inculdes support
      for the "-log-level" flag.
      
      Update CIPD bootstrap scripts and tool installation scripts to log at
      warning level, so that standard operation doesn't produce any logs.
      
      BUG=chromium:748651
      TEST=canary
        - Tested this CIPD version on canary waterfall successfully.
        - Tested "gclient" bootstrap and "vpython" / "led" on Windows system,
          no output and works.
        - Tested "vpython" / "led" on OSX system, no output and works.
      
      Change-Id: Iae316908283c43c504f293aafdf897df83dccf8d
      Reviewed-on: https://chromium-review.googlesource.com/588889Reviewed-by: 's avatarRobbie Iannucci <iannucci@chromium.org>
      Commit-Queue: Daniel Jacques <dnj@chromium.org>
      18aa2d93
    • Paweł Hajdan, Jr's avatar
      gclient flatten: preserve variable placeholders (reland #1) · fc6196b3
      Paweł Hajdan, Jr authored
      This is an exact reland of https://chromium-review.googlesource.com/583617 .
      
      One of the main use cases is making it clear which revision hashes
      need to be changed together. The way it's usually done is one variable
      referenced several times. With this CL, we preserve the references
      from original DEPS, as opposed to evaluating them and losing some info.
      
      This CL actually makes Var() emit a variable placeholder
      instead of its value, and adds support for these placeholders
      to gclient.
      
      One of possible next steps might be to deprecate Var().
      
      Bug: 570091, 748486
      Change-Id: Id47e3771b7163149a4cd427b84f84ece52772f34
      Reviewed-on: https://chromium-review.googlesource.com/586594Reviewed-by: 's avatarAndrii Shyshkalov <tandrii@chromium.org>
      Reviewed-by: 's avatarWilliam Hesse <whesse@google.com>
      Reviewed-by: 's avatarDirk Pranke <dpranke@chromium.org>
      Commit-Queue: Paweł Hajdan Jr. <phajdan.jr@chromium.org>
      fc6196b3
  11. 26 Jul, 2017 3 commits
    • Sergey Berezin's avatar
      depot_tools: add gerrit repo and ref to apply_gerrit_ref() · 5aa5cd76
      Sergey Berezin authored
      The only user of this method needs to apply two patches from two
      different repos in a try job. Extending the method to handle this.
      
      BUG=628259
      R=agable@chromium.org
      
      Change-Id: Ia119780d1323add0094631e5c291b0e7a573e6e5
      Reviewed-on: https://chromium-review.googlesource.com/588008
      Commit-Queue: Sergey Berezin <sergeyberezin@chromium.org>
      Reviewed-by: 's avatarAaron Gable <agable@chromium.org>
      5aa5cd76
    • Paweł Hajdan, Jr's avatar
      Add experimental downstream recipe trybots to depot_tools · 56766f1d
      Paweł Hajdan, Jr authored
      Bug: 644609
      Change-Id: Ie832a443ab9ab2cb8e7a114df67ce665ff6c91f1
      Reviewed-on: https://chromium-review.googlesource.com/584877Reviewed-by: 's avatarDirk Pranke <dpranke@chromium.org>
      Commit-Queue: Paweł Hajdan Jr. <phajdan.jr@chromium.org>
      56766f1d
    • 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
  12. 25 Jul, 2017 2 commits
    • Paweł Hajdan Jr's avatar
      Revert "gclient flatten: preserve variable placeholders" · 393ba066
      Paweł Hajdan Jr authored
      This reverts commit e79ddeaa.
      
      Reason for revert: https://bugs.chromium.org/p/chromium/issues/detail?id=748486
      
      Original change's description:
      > gclient flatten: preserve variable placeholders
      > 
      > One of the main use cases is making it clear which revision hashes
      > need to be changed together. The way it's usually done is one variable
      > referenced several times. With this CL, we preserve the references
      > from original DEPS, as opposed to evaluating them and losing some info.
      > 
      > This CL actually makes Var() emit a variable placeholder
      > instead of its value, and adds support for these placeholders
      > to gclient.
      > 
      > One of possible next steps might be to deprecate Var().
      > 
      > Bug: 570091
      > Change-Id: I9b13a691b5203cc284c33a59438720e31c9ebf7a
      > Reviewed-on: https://chromium-review.googlesource.com/583617
      > Commit-Queue: Paweł Hajdan Jr. <phajdan.jr@chromium.org>
      > Reviewed-by: Dirk Pranke <dpranke@chromium.org>
      
      TBR=phajdan.jr@chromium.org,dpranke@chromium.org
      
      Change-Id: If9c52ebfa78aba8041ce797ff842d09952d0e2ce
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: 570091, 748486
      Reviewed-on: https://chromium-review.googlesource.com/584907Reviewed-by: 's avatarPaweł Hajdan Jr. <phajdan.jr@chromium.org>
      Commit-Queue: Paweł Hajdan Jr. <phajdan.jr@chromium.org>
      393ba066
    • Paweł Hajdan, Jr's avatar
      gclient flatten: preserve variable placeholders · e79ddeaa
      Paweł Hajdan, Jr authored
      One of the main use cases is making it clear which revision hashes
      need to be changed together. The way it's usually done is one variable
      referenced several times. With this CL, we preserve the references
      from original DEPS, as opposed to evaluating them and losing some info.
      
      This CL actually makes Var() emit a variable placeholder
      instead of its value, and adds support for these placeholders
      to gclient.
      
      One of possible next steps might be to deprecate Var().
      
      Bug: 570091
      Change-Id: I9b13a691b5203cc284c33a59438720e31c9ebf7a
      Reviewed-on: https://chromium-review.googlesource.com/583617
      Commit-Queue: Paweł Hajdan Jr. <phajdan.jr@chromium.org>
      Reviewed-by: 's avatarDirk Pranke <dpranke@chromium.org>
      e79ddeaa
  13. 24 Jul, 2017 2 commits
    • Bruce Dawson's avatar
      Use -prerelease flag to vswhere when packaging VS · 5a80eab0
      Bruce Dawson authored
      With VS 2017 Update 3 Preview 4 the behavior of vswhere was changed so
      that it only reports on non-prerelease versions by default. This can be
      overridden by passing -prerelease. This broke our packaging setup. A
      temporary fix was used to package Preview 4 and this is the permanent.
      
      When -prerelease is passed then vswhere will report on all installed
      versions of VS, whether prerelease or not. The script will package the
      first one that it encounters. For best results you should only install
      one copy of VS when packaging it.
      
      Trivia: the original RTW version of VS 2017 was incorrectly tagged as
      isPrerelease: 1 which means that without the -prerelease flag it
      doesn't show up either!
      
      BUG=683729
      
      Change-Id: I98c1acb671dccef7ede4443fbbf498796946c52b
      Reviewed-on: https://chromium-review.googlesource.com/578767Reviewed-by: 's avatarScott Graham <scottmg@chromium.org>
      Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
      5a80eab0
    • 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