- 16 Aug, 2018 1 commit
-
-
Vadim Shtayura authored
Linux and OSX only for now. This also rolls CIPD client to a version that supports pinned hashes (v2.2.5). CIPD_CLIENT_VER and CIPD_CLIENT_SRV are no longer supported as env vars, since it makes no sense when pinning hashes of the binaries at specific version on the specific backend. Also somewhat cleanup 'cipd' script to use "${VAR}", stderr and colored output consistently. R=iannucci@chromium.org, nodir@chromium.org BUG=870166, 874586 Change-Id: Iac67fbb6b5d07dcd81d44536737b03b146f1ad14 Reviewed-on: https://chromium-review.googlesource.com/1176727Reviewed-by:
Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
-
- 15 Aug, 2018 1 commit
-
-
Vadim Shtayura authored
This reverts commit eebc3d82. Reason for revert: crbug.com/874586 Original change's description: > [cipd] Check CIPD client hash against pinned SHA256 during updates. > > Linux and OSX only for now. This also rolls CIPD client to a version that > supports pinned hashes (v2.2.5). > > CIPD_CLIENT_VER and CIPD_CLIENT_SRV are no longer supported as env vars, since > it makes no sense when pinning hashes of the binaries at specific version on > the specific backend. > > Also somewhat cleanup 'cipd' script to use "${VAR}", stderr and colored output > consistently. > > R=iannucci@chromium.org, nodir@chromium.org > BUG=870166 > > Change-Id: I9e61f9f8fbdcf10985c52828b2bfbec64b4234f0 > Reviewed-on: https://chromium-review.googlesource.com/1171957 > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> > Reviewed-by: Nodir Turakulov <nodir@chromium.org> TBR=iannucci@chromium.org,vadimsh@chromium.org,nodir@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 870166 Change-Id: I9aa8e7a7f07520aa69d366c76e4dbccae345bc00 Reviewed-on: https://chromium-review.googlesource.com/1175294Reviewed-by:
Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
-
- 14 Aug, 2018 1 commit
-
-
Vadim Shtayura authored
Linux and OSX only for now. This also rolls CIPD client to a version that supports pinned hashes (v2.2.5). CIPD_CLIENT_VER and CIPD_CLIENT_SRV are no longer supported as env vars, since it makes no sense when pinning hashes of the binaries at specific version on the specific backend. Also somewhat cleanup 'cipd' script to use "${VAR}", stderr and colored output consistently. R=iannucci@chromium.org, nodir@chromium.org BUG=870166 Change-Id: I9e61f9f8fbdcf10985c52828b2bfbec64b4234f0 Reviewed-on: https://chromium-review.googlesource.com/1171957 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by:
Nodir Turakulov <nodir@chromium.org>
-
- 03 Aug, 2018 1 commit
-
-
Wang Qing authored
Bug: 867819 Change-Id: Iff107adb7efe366c5ab58f5221c1b9bf3ebb7d5f Reviewed-on: https://chromium-review.googlesource.com/1159545Reviewed-by:
Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
-
- 26 Jul, 2018 2 commits
-
-
Vadim Shtayura authored
When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by:
Robbie Iannucci <iannucci@chromium.org>
-
Wang Qing authored
BUG= 865294 R= tandrii@chromium.org Change-Id: I8ad56887882b897d605dc92e0e61c17de0a74967 Reviewed-on: https://chromium-review.googlesource.com/1141563Reviewed-by:
Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
-
- 19 Jun, 2018 1 commit
-
-
Vasili Skurydzin authored
Change-Id: I4fe559cb44ccd9c6b037b7b096b088adf652ef9b Reviewed-on: https://chromium-review.googlesource.com/1102718 Commit-Queue: Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Robbie Iannucci <iannucci@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org>
-
- 04 Apr, 2018 1 commit
-
-
Brian White authored
Bug: 828981 Change-Id: Ibd4b31413bcdbbfe9bb1076334c892f1a30c768e Reviewed-on: https://chromium-review.googlesource.com/996432 Commit-Queue: Brian White <bcwhite@chromium.org> Reviewed-by:
Robbie Iannucci <iannucci@chromium.org>
-
- 20 Oct, 2017 1 commit
-
-
Benjamin Pastene authored
We only compile and tag cipd packages with armv6, so armv7 hosts get 404s from cipd. This will use armv6 packages on armv7 bots, which should work. Bug: 776703 Change-Id: I6e54c2f9e1b220ce038a99af1df28cb6c0a9e579 Reviewed-on: https://chromium-review.googlesource.com/730850Reviewed-by:
Vadim Shtayura <vadimsh@chromium.org> Reviewed-by:
Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Benjamin Pastene <bpastene@chromium.org>
-
- 17 Oct, 2017 2 commits
-
-
Dan Jacques authored
The uname was reported incorrectly, and should have read "ppc64le". Update the script to reference this. TBR=iannucci@chromium.org BUG=chromium:773857 TEST=None Change-Id: Ice5ffe1257333b2bc1bfef7da60dcea4ead4d4c8 Reviewed-on: https://chromium-review.googlesource.com/723162Reviewed-by:
Daniel Jacques <dnj@chromium.org> Commit-Queue: Daniel Jacques <dnj@chromium.org>
-
Dan Jacques authored
BUG=chromium:773857 TEST=None Change-Id: I9deb95f7f6c30b5970d74bf3d43df2038db3087e Reviewed-on: https://chromium-review.googlesource.com/721165Reviewed-by:
Vadim Shtayura <vadimsh@chromium.org> Reviewed-by:
Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Daniel Jacques <dnj@chromium.org>
-
- 10 Oct, 2017 1 commit
-
-
William Hesse authored
BUG=768318 R=phajdan.jr@chromium.org R=dnj@chromium.org R=iannucci@chromium.org Change-Id: I2c85f9d30e74cfaebf2718bee075d6a21a6e0421 Reviewed-on: https://chromium-review.googlesource.com/708738Reviewed-by:
Daniel Jacques <dnj@chromium.org> Reviewed-by:
Robbie Iannucci <iannucci@chromium.org> Commit-Queue: William Hesse <whesse@google.com>
-
- 11 Sep, 2017 1 commit
-
-
Robert Iannucci authored
This is best-effort only; s390x is still not a supported platform. CIPD pin bump contains no client changes; just points to a version which is built for s390x as well our normal platforms. R=dnj@chromium.org, vadimsh@chromium.org Bug: 764087 Change-Id: I777246712eea1b39036f3b14b88cbd41c7cf0507 Reviewed-on: https://chromium-review.googlesource.com/661787 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by:
Vadim Shtayura <vadimsh@chromium.org>
-
- 07 Sep, 2017 1 commit
-
-
Pawel Hajdan, Jr authored
On Debian's default install curl is not available, but wget is. Bug: 762568 Change-Id: Ibc8c52676fd5e37ef1b9f1ffc061b2be27ec80c4 Reviewed-on: https://chromium-review.googlesource.com/653517Reviewed-by:
Daniel Jacques <dnj@chromium.org> Commit-Queue: Paweł Hajdan Jr. <phajdan.jr@chromium.org>
-
- 28 Jul, 2017 1 commit
-
-
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:
Robbie Iannucci <iannucci@chromium.org>
-
- 27 Jul, 2017 2 commits
-
-
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:
Daniel Jacques <dnj@chromium.org> Commit-Queue: Daniel Jacques <dnj@chromium.org>
-
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:
Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Daniel Jacques <dnj@chromium.org>
-
- 06 Jul, 2017 2 commits
-
-
Dan Jacques authored
It's currently possible for CIPD bootstraps that provision concurrently to: 1) On Linux, step on each other during download, and 2) On Windows, fail. Fix these respective scripts so that bootstraps are safe to use concurrently. On Linux and Mac, we download to a temporary file and use "mv" (atomic) to write it to the final destination. Concurrent initializations will perform parallel downloads, execute the "mv", and copy their downloaded file to the destination path. On Windows, we use filesystem locking to lock the operation and ensure that only one download can happen. BUG=chromium:739195 TEST=local - Ran in parallel on Windows, Linux, and Max. Change-Id: Ie050d37598da67389f21728e781bd58904ef9c17 Reviewed-on: https://chromium-review.googlesource.com/560521Reviewed-by:
Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Daniel Jacques <dnj@chromium.org>
-
Dan Jacques authored
Make Linux/Mac CIPD wrapper fail if any step returns an error. Include the "-f" curl flag, which will cause it to error on non-200 status. BUG=chromium:739195 TEST=local R=iannucci@chromium.org Change-Id: I3efea3f38c1ee322cb9d63f29819472564107ddc Reviewed-on: https://chromium-review.googlesource.com/560723Reviewed-by:
Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Daniel Jacques <dnj@chromium.org>
-
- 13 Dec, 2016 1 commit
-
-
Robert Iannucci authored
This takes advantage of powershell on windows for a cleanish duplicate of the posix version. R=dnj@chromium.org, vadimsh@chromium.org BUG=663843 Change-Id: Ib23a044ff912e3239b58848a26143eb6575826d5 Reviewed-on: https://chromium-review.googlesource.com/414228 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by:
Vadim Shtayura <vadimsh@chromium.org>
-