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 'e95696ff53'
${ noResults }
depot_tools/cipd_manifest.versions

539 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
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
voocpVgmOy76SPLIKKwDw2ej54o11Fcc07-DWd5VovIC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
HKGlT4YcCOdncPD41tx2qqw6YRDYGilaihiQJOzAADcC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
KHKcbc4iB4IKqSn4chzpaAFhU5VWDVInA_jfkLIDB4wC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
aX4WBjiJ63OQB4c_GuelGO3d6dNLcT4JbhtX9BSRzu4C
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
nJQW96O5aLTPVgll3jj7Ee5bKg8IIdu166lKBO4wGSsC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
gRd2nXmMx9LnJYlQUmVefXxcZ_hHyDmrRdp9DRbgQSgC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
YQ9EEPvdfJiKa_yveB1nm8HZBca5O8ju4R1CUwv1JOQC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
r68g23vv-ffA2Xk55amTiyus6PCmWUiGwkDLuQaewMcC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
fPn_8L5wmLag-uQzSw4LOA8E6qX4enaqFWnPkkLh9UwC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
Xak5_zQXzVE9NJDp585FcjyTHTOxlKxcuFdeOCtAUXYC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
ZSWKaAs8Ru90CssX1nvdYApCcFStjYYyXQ0_RpMG3pQC
[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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
ziY_WsU6yVoboLF8mxp6E2bUSfwEuOfGqRZDqWj6-HgC
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
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
ipwQzoM1wJau6T_KOCoUqBt7VFNvyrs21l1s16k9qLQC
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>
2 years ago
infra/chromeperf/pinpoint/windows-arm64
[Pinpoint] Surface CLI priority flag to depot_tools Bug: chromium:1411458 Change-Id: Ife781433e2f1bf8d37990e6bc2e0108c980f9ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4215115 Auto-Submit: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:e74dd94f00ae6be0c8272e438cd264e9817ad585
peMmYTAzWTqkVIGb7qSLKrW6TTat4K5SMnmfBMqWr74C
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>
5 years ago
infra/goma/client/linux-amd64
Roll out goma client VERSION=260 Bug: b/281448203 Change-Id: I4eb38d56059b6919338afa545917409838892a67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4602589 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Fumitoshi Ukai <ukai@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
2 years ago
git_revision:3435fce1653aa1d611c2834901561be7e6ccfab0
6EmVw4-ll63s6BZJ_IqUnc4e0EhMfmuhZWlym7rNU34C
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>
5 years ago
infra/goma/client/mac-amd64
Roll out goma client VERSION=260 Bug: b/281448203 Change-Id: I4eb38d56059b6919338afa545917409838892a67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4602589 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Fumitoshi Ukai <ukai@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
2 years ago
git_revision:3435fce1653aa1d611c2834901561be7e6ccfab0
Q8Oi9o1glHbQ0OiNLg0j0CD78so89daZ3a3jhTcwahYC
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
Roll out goma client VERSION=260 Bug: b/281448203 Change-Id: I4eb38d56059b6919338afa545917409838892a67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4602589 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Fumitoshi Ukai <ukai@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
2 years ago
git_revision:3435fce1653aa1d611c2834901561be7e6ccfab0
8A_rsX8IeV_S8J6Hn8zfwWab7vLsVjbsujR0vuDNxxcC
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>
5 years ago
infra/goma/client/windows-amd64
Roll out goma client VERSION=260 Bug: b/281448203 Change-Id: I4eb38d56059b6919338afa545917409838892a67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4602589 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Fumitoshi Ukai <ukai@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
2 years ago
git_revision:3435fce1653aa1d611c2834901561be7e6ccfab0
T6Xs4ivcOHmuFd22Lf4mjDNhiZARmLvjK7P1RN2Q35kC
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>
5 years ago
Reinstate reclient Adding back reclient to depot tools. This will allow it to be used for chromeos-chrome builds, and other packages in the future as well Bug: b/270080866, b/242680623 Change-Id: Ibb800a7c36f61312d540ee5595c585493e5e3578 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4273546 Commit-Queue: Eric Lok <lokeric@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
2 years ago
infra/rbe/client/linux-amd64
Update version of reclient Fixes issue where reclient erroneously shutdown during startup via bootstrap. BUG=b:269549741 TEST=Run bootstrap locally using the new version specified in this change. Change-Id: Ic443ba48d4d976a5341847bd7855e7d7fb63cc61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4445369 Commit-Queue: Eric Lok <lokeric@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Eric Lok <lokeric@google.com>
2 years ago
re_client_version:0.101.0.6210d0d-gomaip
QIkkdyLfCLyZpWdJoTC8EgbCT7QcUuClhWw4rL_wcuwC
Reinstate reclient Adding back reclient to depot tools. This will allow it to be used for chromeos-chrome builds, and other packages in the future as well Bug: b/270080866, b/242680623 Change-Id: Ibb800a7c36f61312d540ee5595c585493e5e3578 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4273546 Commit-Queue: Eric Lok <lokeric@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
2 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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
1po5AXHrqwkB6b2FYbzqUYDr7sf-7o0209XtSDiiuOAC
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
vrRipWHKM5Sit7gQqDDeh4Oj-YBKFsUsBwg6-C-4TloC
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
3qUL8-0b8RLscZ0sC6ugFM13-xlYUZTlMqkm69CDtvAC
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
fRLNdi2ZScJa8GamwCI47sIgCjApj5ORmVavhPiMh_0C
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
LZj5JYxD2_hgXAaqL4p4BJd7AIgQgRHAVk8NyktPs3AC
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
LhBOTm042IY4t3-dmzvRPmIdG1am93Ew0idzxp3ARM0C
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
vjWHMneMr7zvKfsk1-z5ySatcJKnw7hskFqbwam0cUUC
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
UHY8-gag4_djxs8nqmesM591dAw0kLhiaPhJndLzuf0C
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
ERKGDCv4IIECJLpY1dbodq7Oa5eIg2HgS6dntRfSlWAC
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
tqqmgaiGN47SZrPrwegZTqkEXgIDFHJpC8C9e8g_5vMC
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
ojD07FK6tipK2_S9YpFcSwrPxh13LOQiOubOnZR_WCsC
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
Hx76JySkZu3Tsv0KJ87-f9suRnsKbMbE9z9W91Jg_EAC
[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
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
SW6ncPyG6lE9aay4kKaKzzhPgOhhqmIP-tWykvhnEeAC
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>
2 years ago
infra/tools/bb/windows-arm64
[depot_tools] roll bb To release https://crrev.com/c/4778910 Bug: 1472863 Change-Id: I7506c53ee42fbb514c0ed41011a628fab316f8c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781078 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b083b65e849f49f5792aae39e04ce12530b48ba3
TdjHejl4U5WDwkv502s8YPIo7YYZXkCSQSyLufXymvEC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
w2idIE9Y_-0aZyA51pMYFiZrJJQy_0669l_diLMLcPEC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
pbNOz7TUtGKt3W_ULWBpkUjTOvwum346CrKicGE4XTUC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
JKzTQIcsm_UzLbXXvga0HZ2tH_q1tZhZtW8ZNprpLMwC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
0kBd-WW4APbZKKCjVlmdokzaGglmPMzz1458M64CLYkC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
fp_h0G3uKwJ-_n0II0aspHVzi4xuGPXKJ7Cqr6XVHTQC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
z5ACNSmSs6F9rP7gsxiDd71rHIGmyGygkuyqgDOc6egC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
kD5UkpxcIPhRpJb5UkqRyn_mWuil6FUPXyNJ2vGBmREC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
e6hVWiqTRL2eIWFOH3JbF9ibR8UyH8sHncofBG6kjWYC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
J9BeINhVISFz4UXyKiVh3zWQHmSR8PlNSsP6BmCzEDkC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
PiAMR9Hh8jS14zlDbi6gut3evAFbIN3yn32N3asqc5UC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
wJFrCrcW6vGROGf8Vf9_AIMB1Tshzv_4kTHFryMQs-cC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
XO4N9glA18B2J3DOne4IE6POcwA9Fp88gO77axn8hFAC
[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
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
6ygD207BD00j60XrRNC12iDmIt4AI7e31GPMpFdZoEUC
[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>
2 years ago
infra/tools/dirmd/windows-arm64
[depot-tools] roll dirmd Bug: 1466195 Change-Id: I29425820f82088938ac7ce5098af1f3af3de532b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4712966 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:84ac80ec64abf5388e9e4cbd4a71b5e0d73789df
pcr1RZDyg3SVhvpOCaQ1ZZ4kHmPdT1J6yb4uZ2ZSwpUC
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>
2 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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
wK-qkJG6wZZJW73O5B5W-qmldoE-f7Rv9lGlvLrVJ-QC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
abG7bRd8jOHcCgZn4DwZDaoIXiz3PdAtjLNEI3I1sKsC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
9TkIPLzpRXYfkL1cOKeUGV3bkAS5FhIZQD4vhKewaUIC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
fWMNOuVRftg6IJK3qWtP3REDap8IlEs8GeGzBxQiJ90C
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
OaZi-l-Z7qvYLOt2uiCbHnAeVkIAafgV8aqj6UZS3aoC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
-AJw5QZYWISOXzLXXoat24zuaRqqU9WCbZB59jJ_bIYC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
SJD1uKof-lwqkXcVCkCXGnGdtf87GtNDJOOQ8uOFBOgC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
V-wne2OFe5ATyx4XrJzHiVNHShrf_TrYsj2C3C2feyMC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
_ERajsHeFxNuzzfCogzscveoKzqZ9ciC4HGwVzcgyHIC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
1goLBy_OW_PoIeoNvBvVAUArrsYVVdgWjVrY_eRUDXwC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
G6kSrnx6wwhg06tJz35FFYBVLd8-CzqAP_5gB1z7xHcC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
noM_lnXNlBDeEeFSRQPCVK9rRSfdLjlm0fdJIReO-a8C
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
AX9y63R0nxVRrX24LSdDcXAugxHzgm9QG5knb6SKZ7gC
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>
2 years ago
infra/tools/luci-auth/windows-arm64
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
lVkrcu4Q8BEII4jXyQaMktfcYDNPEzlP9C39M3q8FBwC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
jToHM9WoQcLAJd5C_Wg6tE8pP9zGcke6OMw0DIrHAB8C
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
vAKR3FdYAuzWChvsSU8YWFvUn4kW0LbZEwzLlgBUkIgC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
Vd63abkSwqejo_5N8qg-q3gY6qNM40PEYCmJNcKsUusC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
aoshKKAvW-i0ESmauDlHqXBe5y63w9GDheR3ue79TV4C
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
EAEgNmQyz79IEGB4LtlGU9SR4fO8VG8ZTRYdAbOoQXQC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
L2zeWurH_2XjCDa8JU7gzQbz76qSWCV-MkBM4KRc_xgC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
Z6lJxxmFd1yB-xanqlgN2W7CVH9-B_Ey46ln869WHLMC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
KveTfou0GCAqCGOTjOOY0umSp4QdDs6PseVAAb090j0C
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
KBD6lzPTeQvF4be5xmaDEOuR_QqshEOfv4AfuJHkD-IC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
z4oy_Er7zs7NTIUWvt94kybn3k8tfyzV94hSOhZujbMC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
7YwrmRPnnkILamRZEdTmGdYYsHqexYiz_CuU4BM0_fsC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
P1MNkYLyjrACtd95daSTD_uMNhGkfhiaFfjAtU0f2vUC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
8OU29EdrDvPLgXDRAYLuknN6xUfZoGZeyzdCTrI1l8kC
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>
2 years ago
infra/tools/luci/led/windows-arm64
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
sK9o5fbGnTnMGrZM4uP6QBcmFRhJwGXrzuvPqjqjAJcC
[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>
6 years ago
infra/tools/luci/lucicfg/linux-386
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
2nAvAIWekwRArCqCrwavv-7cs93NX2CuAh_pkStTpNUC
[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>
6 years ago
infra/tools/luci/lucicfg/linux-amd64
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
WXyIWBPzY4jGDhe7a0FZu-DupO40tAw-nMtqVp8tCw4C
[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>
6 years ago
infra/tools/luci/lucicfg/linux-arm64
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
bRDYWp6_WXEv-hM47Dv7cfmUuhWiU_1mHXBLfR84ELAC
[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>
6 years ago
infra/tools/luci/lucicfg/linux-armv6l
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
dGOSCXQPoYzFR3pUBq6ed-bi9_S7FE37D55GrLQsacEC
[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>
6 years ago
infra/tools/luci/lucicfg/linux-mips64
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
MYcXQInpeXNo-xCE4zLFZGdauKZpVETri9JYwqCOBKYC
[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>
6 years ago
infra/tools/luci/lucicfg/linux-mips64le
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
_KSqJAc0_bRpWb8BVpuTTTMa-SyTPqwGRtc_SoB3X9MC
[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>
6 years ago
infra/tools/luci/lucicfg/linux-mipsle
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
eX7aB3xcEi-iIkg7fu87t021YzKlmd4bEFRjx54jE9wC
[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>
6 years ago
infra/tools/luci/lucicfg/linux-ppc64
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
5-H3k-cO8CboZ-4xLz8QOHj_GzYNQRTyJubMesIudqkC
[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>
6 years ago
infra/tools/luci/lucicfg/linux-ppc64le
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
mHf6TFz1RRbvZdZTquvnv1MFfRs2S8kjEP074fAP6noC
[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>
6 years ago
infra/tools/luci/lucicfg/linux-s390x
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
rS4HhlhXeTJOa2YJOMBOQT7ttCW4WFFOqo81aB0rqU8C
[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>
6 years ago
infra/tools/luci/lucicfg/mac-amd64
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
8a5JIM8zV5kKR68umItuBrKxyOYgQJTHP07j7nI1n0UC
[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
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
vczHVY-2VbcmoU9k_p1qg2WYX-g_gxmYLwkYqwkYc30C
[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>
6 years ago
infra/tools/luci/lucicfg/windows-amd64
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
5pLfojImQAax8D9dqGVfMpH7NjTPiIIHF87ZTnVGY2gC
[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>
6 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>
2 years ago
infra/tools/luci/lucicfg/windows-arm64
[depot_tools] roll lucicfg to v1.39.14 To add shadow_dimensions support Bug: 1469965 Change-Id: I4a9f519333190516609d2f36e538ad1c0aee2d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4781076 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:8afdc8e6f4cf12025a391263869fb4ff84bab810
h2HD4no-PjUz7qcRkbrn2q6n0ReAsOWjHiZUREPV20EC
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>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 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
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
nRUaJj85Xfp87bEW6FjXOde90sf-KhSbhL0b08ZDXU8C
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>
2 years ago
infra/tools/luci/vpython/windows-arm64
Revert "New vpython to depot_tools" This reverts commit 43083529de5802a83f53f1d53d7f5f9615999996. Reason for revert: crbug.com/1470122 Original change's description: > New vpython to depot_tools > > This is a reland of https://crrev.com/c/4653897 > Fixed the issue for cipd wrapper. Now all environment variables should > be perserved when invoking cipd: https://crrev.com/c/4669637 > > 1. virtualenv field in the spec is ignored. > 2. --vpython-tool removed support for delete and help subcommands. > 3. --vpython-tool installed removed support for naming venv. > 4. removed support for -vpython-interpreter. > 5. removed support for searching interpreters in host PATH. > 6. python 2.7 is available only if the binary is invoked as `vpython`. > 7. fixed a bug that passes invalid vpython arguments to the script, > which may be silently ignored. > 8. python_version in the vpython_spec must specify a minor version > (python_version: "3" is not valid anymore). > 9. vpython now requires the cipd binary to be present in PATH, which is > true already when using Swarming or depot_tools. > > Also updates the LUCI_OWNERS to add peep-software-deploy team. > > Bug:1415212 > Change-Id: Ie541a2a60bef829a976a13db9a6732b406c4d878 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4719827 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Auto-Submit: Chenlin Fan <fancl@chromium.org> > Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Bug: 1415212 Change-Id: I6ca32066acd977a293f8b8f42697c383cc2a93fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4751179 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
2 years ago
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 This adds support for upload/downloading xcode with version 15+ Bug: 1457029 Change-Id: Ic9a3754b203b64a033e958f0e9c5dd19fb4bbe26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4675570 Commit-Queue: Yue She <yueshe@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:59ddedfe3849abf560cbe0b41bb8e431041cd2bb
P-QZDNa0TVwuVwDgSBuJig9baBK1aqZ6QKqspN3KLEoC
[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 This adds support for upload/downloading xcode with version 15+ Bug: 1457029 Change-Id: Ic9a3754b203b64a033e958f0e9c5dd19fb4bbe26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4675570 Commit-Queue: Yue She <yueshe@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:59ddedfe3849abf560cbe0b41bb8e431041cd2bb
u9Z_N-UyoWSSmFTMfWjKmkTMQbFw-LwMgvAGFj1yGHgC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
I4hb3OsZfkhwNgfmRbc8mjb6Y7OLjdrhmleN4Js3gpgC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
eWrhG4AyvG7uabtZJTRVZVEXNgctS_qkz5QLHuIbcywC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
RH7U2Y_ku0I3obRLh8jSqnaJGMik_CjWPCF5FvOlmAQC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
UQJoPMTFQZuj0e-kxTf7yPIhIudYceShrVKv_-T6FWEC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
3Gpjanf3yuC_CBSBrsQke8sia9R8r0qF001tQmYopTEC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
gUtVqVqL-CQrD9c9W_rOksNDMqShImnUZWzNaB_FVegC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
rD9DSoXtnBsacUK9EsIpjPOnrId4nfGayVVsKolyPaYC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
wHuhPa3CsbnrFHA3nvb_wlz9Wh6oOrzOg-j1154Yt5EC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
psgkfBIZPbwsWljqSKuUuRlc5hYYHfPIpgUlLWXj1UQC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
630v0D7jfQg1NpvkgHgO76LAPpVC7sfHeOj7g7J16Z0C
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
u1LsDRxpsJkQ-Wkg-jgywzvfIFifCTmqA-xEjB-m1iAC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
UE10VYFCL_5zkHA6K1Cowzqt3P6G5Qx3KypE_IbkKOMC
[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
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
UE-LuuU6e4ZLsD0niWn1rOud8w4OIMwDnIX_s3id-5AC
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>
2 years ago
infra/tools/prpc/windows-arm64
[auth]: Update CIPD to include version update of luci-auth change. Bug:1413615 Change-Id: I17b8a11dff55712dae1d866b56744f4105b2a3e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4657278 Commit-Queue: Camilo Jacomet <cjacomet@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:6e9be28a4c4e3a804f400dc6c2ed08b866f0a38b
[auth]: Update CIPD entries for luci-auth Bug:1413615 Change-Id: Idd371f163a7b927d5e2337779fa21113bdde06f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4650867 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
7KTsAKpNk_UH2oQhHwZYHpF0OpvSoipAZY9qRnMk4AEC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
_Y2m1kyroqbtzb1D2ukTctJmRY_n-akf8iReh8yI68sC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
FMiYxXxW7e80Q05063_1aRUZTmRTN8ZDTYOZIpIoD5EC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
74Ht7j3VFJFDBxP1ThgAyWaLvyfGyUvZuzg8Sbq7p6wC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
LE4Xylu2olxgJBySC2TK6vCDyRxupc3pVLZWkY7ERU8C
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
iPGsA_vRmxBBjc9gdnhEW0yMPpGx7xwWtEu-RRKFfCkC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
jKzygzizl-pR2M0Iax_6JqnHqv3XtpM7UMlcrYdJIYcC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
7kllOu390y5OQ97_ML9z04XFeQ_y2FuztoZPHjF67QoC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
zCOOAsFLyn1_yCzbuoUxE5kO89dhHHbl9VoexHmvtcEC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
6srU3OC6m2fS29qxrixWdogYDZ0lX0-adIvw8Dw-cPcC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
Yx71IMXKheXLtQojfl8rA24WZlhEU73hFQS7BH-w3bAC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
K18bDmcE5Zr7pBY5dtNA6rP3zhR_jpIP4_9RrbkRgoMC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
6TYpzQz27_jMlMs5ghtB3NmhWwhw2uREEUt2UIdZBxMC
[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
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
XQdH4Il3e8NabeLSgwb0VUL0LLRYZIJIkukPpb_ygJ0C
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>
2 years ago
infra/tools/rdb/windows-arm64
[ResultDB] Roll RDB CLI Adds -baseline-id options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/925188ce4861..ea16b97b0d2c/resultdb/ Bug: 1456545 Change-Id: I0c3c0f7bb1ace8f8037b3e91123c33e705dbd631 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4661595 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 years ago
git_revision:2ed07b3775e71f9a84743290144c52f43d0899ec
RueLDru60JHz-Dl6KipnoanPwUEwBAtUz7eF7SSEPbAC