aiden
/
depot_tools
mirror of https://chromium.googlesource.com/chromium/tools/depot_tools
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
chrome/4147
chrome/3987
chrome/3865
chrome/3904
infra/config
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6e096da546'
${ noResults }
depot_tools/cipd_manifest.versions

551 lines
18 KiB
Plaintext
Raw Normal View History Unescape Escape

[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
# This file is auto-generated by 'cipd ensure-file-resolve'.
# Do not modify manually. All changes will be overwritten.
Add crosjobs to cipd_manifest BUG=chromium:973247 Change-Id: I8be6386fc3ab9ce6e8d9558862dfd0a7c74a5e6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1743018 Commit-Queue: Yaakov Shaul <yshaul@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
6 years ago
chromiumos/infra/crosjobs/linux-amd64
git_revision:ed616d595eb7241d39d34907050d2949121d6ae8
_vAeU0Q9lAxn933K8vDhwGK40zKVvV-yXGpIy43ATXAC
Add ninja to cipd_manifest Currently, the ninja binaries in depot_tools are committed to the repo directly. This CL installs CIPD ninja packages to replace them. Switching to CIPD ninja will be done in the next CL. Also, see the performance comparison and CIPD packages in the comments below. https://crbug.com/931218#c84 https://crbug.com/931218#c86 Bug: 931218 Change-Id: I44d5e9ea1447588b32a10db20cfba088dd748f48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3674981 Commit-Queue: Junji Watanabe <jwata@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org>
3 years ago
infra/3pp/tools/ninja/linux-amd64
version:2@1.8.2.chromium.3
PUvdixKxFO_KVk9d6WFpXLVDMM0MHv86jyyySTMQ7KIC
infra/3pp/tools/ninja/mac-amd64
version:2@1.8.2.chromium.3
w-R-1UrTQJ2UPgSjcqXMayjE6pf76XpXE434rOY1EC8C
infra/3pp/tools/ninja/mac-arm64
version:2@1.8.2.chromium.3
nVO-Kzyky9nfG4pRb3Qo7KdxyoEXjdwuOhVwy-h0rbMC
infra/3pp/tools/ninja/windows-amd64
version:2@1.8.2.chromium.3
HLdWFKyFMpFQO3VFSps1gevQGwY95hEBUFblIfDux5QC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-386
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
K7ISVpbBGQ1aldta5pTu5d55qpy3Z-0-mMWvOsIoXPwC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
FQb9yv6RpaFLKkoQfgve2prHtgs7sbiEE43bBEQmg1EC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
FB_zQHJ0X7QCfm0G8XkRt8Df4BpV20G3bUi7U4Lb9kYC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-armv6l
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
wLj_onh3aFYxDgjnAuj_REw8X6FGatw6HVCObpJ38gIC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-mips64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
JkEKfj4D5opr9dSF5h1m9KSL9rNCV-WM75qfVWMl6F4C
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-mips64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
zdTFJnkFf21ka2YNCP0hV9kYi6mv7BGHp4Cw-AAynHcC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-mipsle
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
r57nlI6fLX56ghNGTvzOQzr3bWTHMLun08Cf5_KtsvwC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-ppc64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
0XAxWa4Dv2Z4MNdjoCzIn4AmjajP3cEB3MabTK8MX9sC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-ppc64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
LvFMpFqNnvqKrW9OvGdNLjcd_AyeoZyfYI2g90w6SUoC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-s390x
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
GjhvUzbqbe_YWBGyNV75Bok17F1VufqBKSPVHrR8w5cC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/mac-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
QXeE7CCcFBqYj6wRgXoxwF7EReO8RGI0Ykyy9-RrvGIC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/chromeperf/pinpoint/mac-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
gQHv0UMDd8dydgzMPKndkraTGXJwug-OL8X_yxhfbmUC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/windows-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
hlKSh7FVQsL5gHDXcY5YjJ7wDIa9ZW8Ln5-TUgchmd0C
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/chromeperf/pinpoint/windows-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
grRLh4CDzVQBWdB54xiWZMIVsQ0WGp0VdIfGpre0DzgC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/linux-amd64
Update goma client Bug: b/260020400 Change-Id: I6318481dc400429ab34cbd03b0b52bcaa02c4ef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4189284 Commit-Queue: Junji Watanabe <jwata@google.com> Auto-Submit: Junji Watanabe <jwata@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
3 years ago
git_revision:b493c375e7e891ed1eb4ddb4f8697df577fe2995
_wCBhXhNV4Zwaegv2ZWtv8kHlVdNWFp08uKVdLAaFdAC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/mac-amd64
Update goma client Bug: b/260020400 Change-Id: I6318481dc400429ab34cbd03b0b52bcaa02c4ef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4189284 Commit-Queue: Junji Watanabe <jwata@google.com> Auto-Submit: Junji Watanabe <jwata@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
3 years ago
git_revision:b493c375e7e891ed1eb4ddb4f8697df577fe2995
nE9vLiu336rHu5QHoeK9H-5IlG554juBEO70Di4BtZ0C
Roll out new goma client binary VERSION=216 Add mac-arm64 platform to provide goma client on fully supported platforms Bug: b/182514677, b/183118231 Change-Id: Iae7581883d403a1a28f7d0bb1b871c9cfd0f7e65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2816481 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@google.com> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
infra/goma/client/mac-arm64
Update goma client Bug: b/260020400 Change-Id: I6318481dc400429ab34cbd03b0b52bcaa02c4ef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4189284 Commit-Queue: Junji Watanabe <jwata@google.com> Auto-Submit: Junji Watanabe <jwata@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
3 years ago
git_revision:b493c375e7e891ed1eb4ddb4f8697df577fe2995
FRrdVdPVhcoJZVEu5PIAdNAFAFBlCmoEQ_qad4nmhGUC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/windows-amd64
Update goma client Bug: b/260020400 Change-Id: I6318481dc400429ab34cbd03b0b52bcaa02c4ef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4189284 Commit-Queue: Junji Watanabe <jwata@google.com> Auto-Submit: Junji Watanabe <jwata@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
3 years ago
git_revision:b493c375e7e891ed1eb4ddb4f8697df577fe2995
QIackRy9RePbN-44PAUxNCp1MgI-Uiu3IaL-m6D6Cd4C
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-386
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
UfyjFoDX6SK3HOkK3iffM-D0HqhnxLY7akDOr6ThfqcC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
IqaNTqEvnCoVyw5AfRSJt4bL7fvjP7ghmHvl2rdj1l8C
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
ZNiGinhhL7zYVU8-wYz11QW0HM6YUSFCprMv5I-2DIIC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-armv6l
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
jyx_pT9226jeiSCf1oskxPcZFKdQoOnb3QwwHJjQ7HMC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-mips64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
nQ-LnW8z8Cd419ELouZ8sv9zUjOLdhOS0NQJybzMtTMC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-mips64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
4OM4mqx99aV-pBPprULT74rhVspswWVWvkr9ZdoSo_4C
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-mipsle
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
Od38R1h-11fKOoR7ObM_JHwIcIIRvvXjQU-uOClyUfQC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-ppc64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
Oa177zvpH0g6LUcX1nHe2PElTEXTOee4mGwvq1PK81cC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-ppc64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
2TsEbDaESStvI6Vwx8vAFcFqHLDT2qaqu-9vnVIdmVsC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-s390x
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
fl73iG7aHr1bJVXJC5zO9SN1byrd8ifww6RsRM60EhgC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/mac-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
erWNc0TXuXFtp1T0Ect4Y8JkxlnZ99bOVQ7sdltKXvgC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/bb/mac-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
6mTGW8wk8SemzvtEvsiponw7UCtz09mzgKlKqKxY0tgC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/windows-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
3h0s0o8vFI0JM3MQYTusvxrpZRU99PMSIP1Q4A0qnHwC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/bb/windows-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
UyUuLe0hnvavjAxJJHRN9lF7AGeCrjE64XinTlVF0kEC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-386
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
F-U9slvT2L47tjXkBtdX9iSAx47q1uS23OAI1XgqIrsC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
ErmICyViVM_Sm7M4PHsK5mtNdozl-78aPHUPK9NEy2EC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
hX8D6e3U9qRbWXGFsC_R_iJkvuvJI5cluuVZbD2hxUUC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-armv6l
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
Bn21DVXBbfXBGDubKqZcg0KWYxyBdBN9OVAKMYRDmFQC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-mips64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
UBByaseg7wnNolR4HQSN-CFI1WC5jm3Y56eNw8TMCLYC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-mips64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
t16NYJuDfE5Nedgc9fa9DF_a02nXN09lqOriw9CMik4C
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-mipsle
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
iJ0herfUwTO8DLwuV02a_zPFAvwKrT4J-aewL11Sn0wC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-ppc64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
zZO-HkylmBOqHx8zlqrer5WQe401gKHcT-IXjNyLi3wC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-ppc64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
_c_xJzjq7s2aL-2DEJ-jzhgu-sgKJ8gV1b-FAtnQnAsC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-s390x
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
SfAatlzaHPbPOnq_9FG-YzzITRSIl6A1Mv1rs08vD3QC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/mac-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
aZpmmwjGZ6pdLkHZ8qulz02wcvMD_aRPy_gqnTJIpoYC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/dirmd/mac-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
6EPK0FO8auiNgXp_LqBkIsmUajdgj9k6JnEJdSbt_hEC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/windows-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
lYYy3Dab8ID4DIS07-wJnbdi05N0QZOVNfuK6QDJAVkC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/dirmd/windows-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
CoAQMhIaxyZIIC28OSkLhgUQ5nb3duR3qqE2zIkuywEC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-386
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
YpQweCHVOmXrSkmEO6UeKq9powKQPafFd_xZI1DOVa4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
z0G9-JY0EO2Jm7rARIP-DAw_d_pVofosMFTFhsmcSnwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
4WMk1ODcWIqvFkzWjmltV7Dh2xrb2jCuOVydtByXvCMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-armv6l
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
9nWO2aDAjvrRdldvvihegSulmqQaQn31wbxFcbshi4AC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-mips64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
3nv5iiq5_QZd3S8lqMnauPxzK41p0aOxzko-UDvend4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-mips64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
FF8DEmXcrfAl-FrT1TuoSCUOTWwZE2cQ0pXR5ffY-coC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-mipsle
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
A-YQGABuDVgir5OZKeuUtxV7Tb6HauYLLNpwuBKLoG4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-ppc64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
QA2h7hFCCIMQpogFLo9_mwa2hpF-qqmsutQMCHcPmXoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-ppc64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
7f9wW6AHQq95FcdpvmZo6Y-CqLc1ZFfqEGYaZZELk9AC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-s390x
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
A8tng1_noLfOdRw2pJW_HHk-HBV0uyZLFPl5cpNKmb8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/mac-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
CG7NlOjLL1Vm_5_dGVb1UHlk0ZmBEBPEM9l4hw4GKrwC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci-auth/mac-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
9RI8YWtWl9AGmFHjg_LCSykJmt8EOxjnHQl9Isuw4NgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/windows-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
vnr1QAp8vUYKu_tuyNW4_cZZWbStq-9NX4JqMSEyJRcC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/luci-auth/windows-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
3g1eBtJpNxifhLSddADS9DVxQRVctVAObujwXmshY54C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-386
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
diWjyrmaLzExOjKMJoAOxKmbLPbMHtV3A4FmpBkX4hAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
66htq0QXzzEUpgPWJYJh8RcSUD_fBacBe6WoeNWlcREC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
esrLozfTb7QBcN5h7PmSKafinTbpWC7klz5oXlHGcyoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-armv6l
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
QMLlhgZtIHK3Ltny-96D4ifORxOOgSf1gO9Yhc2TgjYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mips64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
4Pwo4wOKWg-1PlOsHvzZGG-vKbLqjihjy0c2iStcFGEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mips64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
nvK2XJ-WEM6Wg8kuaOq99ecrBWX9bxtDoOPVW-B6tIQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mipsle
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
pxnrNW4vExZu9j0s-Ptoc3g7-RXGIar-4rRRlyoFC4UC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-ppc64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
JynbdShqALvAUaZISMlmZ8I_jj5zVC-Cr4iptAvHsOYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-ppc64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
Qupq0HcYaVWYLyZCuI2_yFtW1P6AN3R2Qn_YJTfw65gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-s390x
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
u3mJXTWjPL5Z-3_EEwAO6mMnNA6cU2xYcHeSpn4OfEAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/mac-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
2nweWY_vUEc1wixPH7IROfs57_sTrkXx-frzHXD2oT4C
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/led/mac-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
y1OJHj_sbXmoBFTZKGk_p4uVrg1Wd9g-4iDuv23f03MC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/windows-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
5rzNSLB5wgwsSjXa1W7VTdoH7XQqXiD_pz1kyzWg6YMC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/luci/led/windows-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
rr03rcka9N7tcJk4FU9huhj_3OyA5KndQ8YuR-V22pIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-386
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
3uY7Eurt2mPgb3flE3ZYuXOYkwBwihEGAQZb-0mlnb4C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-amd64
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
E1RbmLrLnptv-FOdCob1P44ZmG4yKTW3Xjpnn2qiu8sC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-arm64
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
QRpNuYHfWEQzhksT91TRl_QvpW58Me20MrC_4F3vCREC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-armv6l
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
WHon7yCJkuHptIYftj0dLz5D6zsdjegi8MwbDDA2YLsC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
CJ1AmFFIPOqLrObSZW37CrW-fCcXZHKXH-UpIHw5sXIC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64le
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
AIBpmZ7A1-ROzHO9aNsbEBZkuxQGg_DB1dzpVmTJ_QYC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mipsle
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
Vd-AdzdCG4qsVXcaCZSPvzezjQ9HOzvPiPw0OV9SfpoC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
jk7_rAmS5W9jiW6PQulZ0CtUIXNezuWlmPpcg704Y4IC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64le
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
lbwpeRH0HYuK7nWmnkDSlFvxrg6-ByLo8Nu31bs88mcC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-s390x
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
uhoAo_pDWdMeQx8d09RHxrhxrdQDUha5KG2v3k0FzWoC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/mac-amd64
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
hTDSnFAnzRPxxtmXZ0yopOzvxWOupQ0HDjMP6XV-gbIC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/lucicfg/mac-arm64
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
tYCfNznVHLzZvGqveybvtWlioVSjQu4NwS4ZMH9-MOQC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/windows-amd64
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
ewYXubyqlag83H7udtMDeD8J8nfor1vSLdNp4JQsXp4C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/luci/lucicfg/windows-arm64
Updating Lucicfg to Version 1.38.0 Version updates lucicfg fmt/validate/lint to add conditional formatting rules based off path. Change-Id: I0870c142210f95e75356ef2cc9d94f4e265f8c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215131 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Riley Wong <rgw@google.com>
2 years ago
git_revision:dca1b4a6d6c11d64f3708a2e4af8d2a3f4e57c83
c_lWoNQ_PVyZSeM7WsENg4Ea8BlV3xvPxi9xiilYufIC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-386
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
eGwM15U21ZJfAQUr3fwhBXJjbs0C9R5PhQ2s7ffJ5x4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-amd64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
9yAXv0KsU9JAgagYQxkjWkU_YUDsDJpdQ4Rktg-EJDoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-arm64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
caLUJKwXkeJqNbXe8VrUaJapyclM4Pi8UqrVMDYRvqMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-armv6l
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
4DqSKhlfFqV13-5gC0ocY9p6ywv-cJiL2NilLkppLiIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
N6eu72sj__hX71cv_zxtnmskb1JPT3H5peTA0A4hWQ4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64le
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
2fVbrtfqruPr0fCu6WzUd6F0ZzZOAeSewpvkvK9qvl0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mipsle
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
44Pd9YZvAOGgXkir4GV_3nfWF6DFFOx91y7hrdeKCpgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
2bF-o3-L4WWbUHR6SvsVUAq6X8ZcQvT0GD762sM2CYEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64le
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
5eTfzvKq0RH3XgWLuhKPyVFGwbYi3fWogKENRq2wx9MC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-s390x
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
y8M08KKGmPcQtUc9O3ISZAvG0cXSDvevJrk59xhC9j0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/mac-amd64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
Jdog2fhqcbdX7c8uZTwC0ED0Z6Se8-Qj0IKZzzfkTqcC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/vpython/mac-arm64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
5od2TokCifZKqqmc-6P-rVJHCbq9-3ogCbY8M3SRFooC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/windows-amd64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
nRUaJj85Xfp87bEW6FjXOde90sf-KhSbhL0b08ZDXU8C
infra/tools/luci/vpython/windows-arm64
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
AHTqVMdkiBvkdKKoeo4Ib8z-ACkfIgRuKFos3WADrlAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/mac_toolchain/mac-amd64
[mac_toolchain] Roll mac_toolchain in depot_tools to latest version Including the following change: 3949129: Fix mac_toolchain ios package content | https://chromium-review.googlesource.com/c/infra/infra/+/3949129 Bug: 1373792 Change-Id: I9a0a037d495f8d1eb4ba838b7312e5f6aedac02c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3949012 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
3 years ago
git_revision:febf962fa9e6f5cc5c4ce86e8dab6ff6d91088dc
QT5Z7SqtISM6t43Aq2EfIZhPsoltf4I3TL5_VjrhGmIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/mac_toolchain/mac-arm64
[mac_toolchain] Roll mac_toolchain in depot_tools to latest version Including the following change: 3949129: Fix mac_toolchain ios package content | https://chromium-review.googlesource.com/c/infra/infra/+/3949129 Bug: 1373792 Change-Id: I9a0a037d495f8d1eb4ba838b7312e5f6aedac02c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3949012 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
3 years ago
git_revision:febf962fa9e6f5cc5c4ce86e8dab6ff6d91088dc
wN2a62YXBByoREz7owfdlpk47efG7dq43ApwhSYY9IkC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-386
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
tjLmiTmKH3CQgyHYUpffhKuBjSgPL7Wtgo1QElWe3xwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
1daA634erHcfPCC3w2-YWCDNMj_i6WxKIMHAyR06bBkC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
0xyn6ELqWyI_7eLg9Q7aEGZ0p1wEK95D8vO7dj_gE_wC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-armv6l
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
wYIzsztnclU_LKHBfTcn9daypSfdCaq0fH22S6U2VdQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
BWP_WP-0Xa9YB67eNPPP0H3BDPKXa6HaAf4C1RO3KLAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
5uYRtgQiON9uoSg0bleX7TsdvgsI4iLrVaSEnSlRV7cC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mipsle
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
0ySypx28FtJooKe4236n93RAVdU2NmyBllsMrMYcnZsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
qgPz8DsWlotJSWmdM5YQQYKZPr2KRsDJAwFRmviJ6EQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
ZJEQ1WtBJwRtjF3WU3z3EGvhiH_ACxKXTxPyeFpKEDEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-s390x
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
SXOvREMHaD5eLdYWaJfYW8wv3wWZCVkEPGLiMWVZF5IC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/mac-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
Am4xFw04qSa_UVMSA-WE9EeudA8_9Cs1lt-80K2cwywC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/prpc/mac-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
K-fBxjXUjKLrMV3cqc8hrRpr7zvLX-iEN7igzZq4K0gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/windows-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
eqxvBHyAjHaAqIpaKsbtsfOOtpWoGr3_9VQCckYOaiIC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/prpc/windows-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
YZumboffAhxRLQfEOwv6uc8-j7U0WSX-96b7a2v_qRcC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-386
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
h2oQz4UDKxCg9Af_Xu7EEl7iY6dNW8uMwni9HuflB5EC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
aDXfwGq6nieiN6q1ErKq1_7QKj1kPe9SbYua-dHDDWYC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
6nzpibnRqUM0PNRCDtq4kKdtaNc1UXeQ6b7vBEMXkkMC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-armv6l
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
prYhJI6KMOhfCeoU8DbvK_a2-13fnWwb48oFNPVrXFEC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-mips64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
4XEPn2TJg3Xqp9PZ1dNnOnxHY0DIppFItOnwG_mLoXgC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-mips64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
X24FbIs9bTN0eBxZ6aplvYklLCETk8GVEAuLzGWMEIMC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-mipsle
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
mSX3wXzQUmDqy3p2fR9wAi5SJWEF4IUWL2oBa3JZ5cUC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-ppc64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
okLIELnc_wMlrruzPT-8DGt_JM37tkafW24WfpgtagAC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-ppc64le
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
-coypW7v0xuu1f1LNKN_BK_T_DigfI_DW3C8peqmF1IC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-s390x
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
fnkDDEB7l0C5Z-jZH6_RJYuImC5nUVV4aEGzouewkI8C
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/mac-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
S05T0TFAsjNDk9GinafjAGZ2ogzT5VRzYRGlvcCZaZ4C
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/rdb/mac-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
PKTaYIXawMYBeeQOeY585VyidT50iLR0uN0DqXCBtVgC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/windows-amd64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
FvsZY_uzRfB9sOxMDVqOW66CPbwX898ftagHgZndNTkC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/rdb/windows-arm64
[oob-deprecation][auth]: Update LUCI Auth Client. Per go/oauth-oob-deprecation we are switching to go/luci-cli-oauth-login updating the packages that use luci-auth. Bug:1406354 Change-Id: I3fc0fd2cc88d395f28e080d90aaaaae672c33da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4195020 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Leina Sun <sunxiaodi@google.com> Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Sean McCullough <seanmccullough@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
3 years ago
git_revision:7c22b5fdaf13b03ca7a8cf80fe02e625e555230e
F3tegU2qYCVK8JM591gcORgYCulV68kQJvFLgMKDVNcC