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 '48fcabef4c'
${ 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
3 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>
6 years ago
infra/goma/client/linux-amd64
Roll out goma client VERSION=258 Bug: b/267569038 Change-Id: Icb58c9cc38e7bffa55b11d434e3ff45efef84114 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4305079 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com> Auto-Submit: Fumitoshi Ukai <ukai@google.com>
2 years ago
git_revision:41b3bcb64014144a844153fd5588c36411fffb56
c_Q_j-Ix-CPa3xDl0VVLlnHgcEZdZlDnjh-57g_5QRYC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/mac-amd64
Roll out goma client VERSION=258 Bug: b/267569038 Change-Id: Icb58c9cc38e7bffa55b11d434e3ff45efef84114 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4305079 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com> Auto-Submit: Fumitoshi Ukai <ukai@google.com>
2 years ago
git_revision:41b3bcb64014144a844153fd5588c36411fffb56
OGMNN5LEVA61tZz9UBqV9t5UV4UkD1O5rTKzmcQlzhwC
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=258 Bug: b/267569038 Change-Id: Icb58c9cc38e7bffa55b11d434e3ff45efef84114 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4305079 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com> Auto-Submit: Fumitoshi Ukai <ukai@google.com>
2 years ago
git_revision:41b3bcb64014144a844153fd5588c36411fffb56
oRX47Xvcc33kLoJEbu3J7J6-xLQ3wxNrCP7RKIQSpmsC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/windows-amd64
Roll out goma client VERSION=258 Bug: b/267569038 Change-Id: Icb58c9cc38e7bffa55b11d434e3ff45efef84114 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4305079 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com> Auto-Submit: Fumitoshi Ukai <ukai@google.com>
2 years ago
git_revision:41b3bcb64014144a844153fd5588c36411fffb56
AChoXxs-WpJXH3jFYC1ePMbpQrIODlr7U7nWTloaDL8C
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
qwGtorYfxE2GXxU6faRp4xP95EH2NyqDk93HDsGDR4sC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
5duiB10Uqn62EMxdRNF5q3KXkm3XOUrM4KUhc4KpmKkC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
ii5vEtJTso0VKxbDVaUeGXOSrVbiFbgGkIKzXAb66XUC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
f53nUCjvXmWFZiwFBMy3MatgOx9t6Eb2LAKwAoBf1JUC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
hOi_W4BldgwKaOGJ9k0v5rxYfcAaP8tEnsjtDnuui_cC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
MtHAKatID1KxDMdlGZtCpTMoJPVIY1S762-qIIcgPUgC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
cm8Q23kfFwf4AlgWUxUSMcKIUCZtnYLxkBrfU6A7YQYC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
1QVllc1ezPP_Kfe1jwQCZKUPfsJ5aB_eedrpUkg26VUC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
RR6ZvIN0huAj0mICg6Q_FyHe6unEBQJbtcxuEfA09GQC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
KoIZxsQ5tjBpgGgx0G-k6794DzTiCnC_EbbaHXnNE-QC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
tlEdNfQ7TRwuGdot1AswtCc6lBjtOM84MK12kFOmQdMC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
jelGg7JOo_tIl5r-2-r3KuBRlWs4ssDcdcdiC9IYwfUC
[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/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
1x0JrBLYxDJEVjIAUPvhmqFgL0wWuYUWcE1sGrrnI0IC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/bb/windows-arm64
[depot_tools] roll bb To release https://crrev.com/c/4424857 Bug: 1430324 Change-Id: I0bf8051f9b716646cbf5a551bda8caf6486d0f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4449948 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:d791252214c1c2c6b5fbdd773499781622a82529
oZP2IosxvlsUC1FWdbLXt-mRGppot8sNxB74pdE9nHUC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
GI3ojsFwtQt3F5BsNDmxnbEecjKhYaY-UfBvsdyuPAEC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
z59HyedxgRs1WGlDc6l8HsGLErnstLGEue04GG5I0OYC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
6OYZzWPOq_5HJ9zoFzc_xNBkLeWndIrKVv9WW2Zv6vcC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
m8-plVTxpqXz7RoH8JN5kk7c_4WTmxI8DdVTySHre3gC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
mbouGqUX_AYVPG2R9AhW9QCIl0IkHqVhCpPlLt2m4VsC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
8SxyaUDgXjhfyPrkUp3MBDiSDQ-Wqdrr952eJohrD1IC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
VJGRjJ82-qMBLy4oRu0Oe7odHI4-Hu3jcZH5dt02KN0C
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
s2qepKq4m94iPqMhy7tIKIUvG-CIDajYQK-0HUh8KP8C
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
_e4u5ESMwVACoIZCCS1ri48Rq49eUKvOltjJN2oFXsQC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
a-667kvB_OUDgnCbfM83SWNEByJ_kv2OJtDqJKKJ1csC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
w304DtTB7t6z3mISjpi_WKn8hIePyU3Ddnvv3zTjNc4C
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
k4S1GErDE3OfjAjbxdIY9iZOcr8NqT2zf33fy2rpvPUC
[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
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
l5E-9hh1Jl0FsT5hxsddFU25iCzkAGNDcY_9ZAjtfsoC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/dirmd/windows-arm64
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
n3a78XVuPnERFSyr2thyWTGgVmBGPtA53PeK28ujok0C
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-386
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
BGkLEGlB67_Dvl0dpDYv5NwfRcYlthrfM-sZoYYirQwC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
mnuiL0nWrfSc_1Ah8h7d8w9ZFpKEyhIvjuOEP5hiHXoC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
AwT2QyFpGspxSVOhQ15pp8XiaLrhVS-mDgOxi7_Iia4C
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
iKfJNK3j2J381ozo1jg72b_YMng4nyH-eDnRQF2Bz6IC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
PRTj_wNzcwziN2BuekrTOCmJx4cxYGH-bem9XNQssd8C
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
G-kqjHV8bdGbGXxz01-aB8bfLJVhl2at_FU0aw-1eugC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
zcj2o1GL6sxyFBWrX4aotlUzHlz-D7SKji-gIAXAM7IC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
PJoDgCGe9xu1kBjqJabMJZRDP4U4aGgcIrcCRcvShlwC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
_SB6USWqevND1NFTw7aF-1r8hu1OM-dVoQZtjYQ3-GgC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
et1U91A4jzEHbAtfne7pv2YmNKhA3ovKqWdqMhFX-o0C
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
LbCLQ0dBL7b6wUiCHJk2Eyf5dJ4eZ2v2kLuGxylVCTQC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
9WS7nZ8QV4fAmQb8XTy8FKh53eUn27DF0Tv1S8URJywC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
QF1DB1xDSZuBOjgeM5UeXhIop5JcGC8SVPMGQ2OW-IEC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/luci-auth/windows-arm64
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
-8CFlGuQ1vh-vdQ4dKRjV2vhFyqYhLvMHwalJwd3blwC
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
wzXSVrY8_c3zkn-X0VVX9M7W-b42DnZAz_Cc1zdKM98C
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
_C-3kADdlV-BUxrpOs0jBRVxHytgNmgjAa0bBYo6Ty8C
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
17cTZyLQAskZ5NBzBBauV0Ut9jQ-fqxqS4QbW8o2gaUC
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
JF5lXJDyNYH9xB0Re_qts9zj_rW123rN1Tvuzhx1fUgC
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
ttF8MQHmdBp7BeVfFp8CDS4tFvErYR9p5viujdIjQc8C
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
LEMitoWs4yKy4Ei0QGWtPuy8K9C7KAF0cgWouNbtnuwC
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
GSOFXEEBLYCwqZpuJtyW8k3l4awSMxORpY14yYluL50C
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
6JWvGd0Ck-uW079zK5kwR68Axaq0JYNzuiZRhsUr_6sC
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
Go0klgMzppIQagI9iqTVnmVWfYdwNHj4BNFSp0GUszIC
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
g-VHFV5mb2kYUmi2DWpMbTUlbPOI1LND5ye7CV_NWOEC
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
7LRxANaABotlEjNDdMmcB5rUKWx5-FvHdlgPKCTbT4MC
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
aFmq5lcKxMQOAcjLYwvFPekdWrbCS2RVYRccJGi-ebYC
[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
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
7mNFDDXQgsUMzrOL3BjDnBYv1gvy8jZ2OiZvVyPoj3EC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/luci/led/windows-arm64
[depot_tools] Roll led To release changes: https://crrev.com/c/4438369 https://crrev.com/c/4424854 Bug: 1434119, 1433082 Change-Id: Ia6ecaca76beec1a85650a2ee60192d3be40bad8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4442747 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:5996f38bcf1d53582b3c62711271dc92782ce43d
BaiG2mken3mRjCrfWOX60hbGe2bG8WCIjeIjkX5eF7IC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-386
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
XhQODtL9qJhPV5lX641Voe3oWs51hwrziHFIOdh93PIC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-amd64
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
qcUTBPCsOUpPyeTBKBO7EmcY16BtUYGz8O2RY3a5mw8C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-arm64
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
ct9DMDzOzpaWRUbwix-2bKBc-Yqz_3ho9Spis0QDBikC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-armv6l
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
0dRAzo8oYcJVmwEkMNeLEUyrw8cJK39F_QfhvAxZ8dsC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
c61tDu7F0xdpSd7OrNqyy-bvSjKwoX5T3b5ysEOhGXgC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64le
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
TUj4sJVj_OiZ_RFGmte2UqnxIZW5zkS_faoqVjzcYqQC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mipsle
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
YT7Ismmdne6J1XYYU-WmALiLrLjoZ6CQErlVFTBdOgIC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
VHBXFRg4HegAIxoo0KbntebGomjey_t36v9fe07rBU0C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64le
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
TYEIW4LKLeOSIsAutfaDXtVv8FPURZINzGWoXCFK7RIC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-s390x
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
zDdO6jgVXfBpHiG1KY2wUk12wZgX27TPMo56ZqHQpvsC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/mac-amd64
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
pGvJcbjzR59YbphTRj51B-TaN3cQt2OLYFr3Mv1HUNMC
[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
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
tpRrr8IFNefgDHuhrd9CiuFGaRkGHg3FCKcVw-YGaN0C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/windows-amd64
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
gBhaSXZPtQPBH-b4LjIEwQNjaOLwuB9M2m2wKLrkhC8C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/luci/lucicfg/windows-arm64
[lucicfg] Roll out lucicfg 1.39.5 R=rgw, vadimsh Bug: 1417086 Change-Id: I2416f5eab5e8a6d653f4db181443c22d0b0d893a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4455283 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:c80314c5ce3ffb422861edd4f8531f5c94c5ba18
k640phpe4EYWAV8dmPqoTmVUlgpoc50Ui6cY4jHrdN4C
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-386
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
eGwM15U21ZJfAQUr3fwhBXJjbs0C9R5PhQ2s7ffJ5x4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-amd64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
9yAXv0KsU9JAgagYQxkjWkU_YUDsDJpdQ4Rktg-EJDoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-arm64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
caLUJKwXkeJqNbXe8VrUaJapyclM4Pi8UqrVMDYRvqMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-armv6l
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
4DqSKhlfFqV13-5gC0ocY9p6ywv-cJiL2NilLkppLiIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
N6eu72sj__hX71cv_zxtnmskb1JPT3H5peTA0A4hWQ4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64le
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
2fVbrtfqruPr0fCu6WzUd6F0ZzZOAeSewpvkvK9qvl0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mipsle
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
44Pd9YZvAOGgXkir4GV_3nfWF6DFFOx91y7hrdeKCpgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
2bF-o3-L4WWbUHR6SvsVUAq6X8ZcQvT0GD762sM2CYEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64le
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
5eTfzvKq0RH3XgWLuhKPyVFGwbYi3fWogKENRq2wx9MC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-s390x
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
y8M08KKGmPcQtUc9O3ISZAvG0cXSDvevJrk59xhC9j0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/mac-amd64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
Jdog2fhqcbdX7c8uZTwC0ED0Z6Se8-Qj0IKZzzfkTqcC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/vpython/mac-arm64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
5od2TokCifZKqqmc-6P-rVJHCbq9-3ogCbY8M3SRFooC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/windows-amd64
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
nRUaJj85Xfp87bEW6FjXOde90sf-KhSbhL0b08ZDXU8C
infra/tools/luci/vpython/windows-arm64
git_revision:7db81fdd219325d5d11fdaf56357ec28c26fffb3
AHTqVMdkiBvkdKKoeo4Ib8z-ACkfIgRuKFos3WADrlAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/mac_toolchain/mac-amd64
[mac_toolchain] Roll mac_toolchain in depot_tools to latest version Including the following change: 3949129: Fix mac_toolchain ios package content | https://chromium-review.googlesource.com/c/infra/infra/+/3949129 Bug: 1373792 Change-Id: I9a0a037d495f8d1eb4ba838b7312e5f6aedac02c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3949012 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
3 years ago
git_revision:febf962fa9e6f5cc5c4ce86e8dab6ff6d91088dc
QT5Z7SqtISM6t43Aq2EfIZhPsoltf4I3TL5_VjrhGmIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/mac_toolchain/mac-arm64
[mac_toolchain] Roll mac_toolchain in depot_tools to latest version Including the following change: 3949129: Fix mac_toolchain ios package content | https://chromium-review.googlesource.com/c/infra/infra/+/3949129 Bug: 1373792 Change-Id: I9a0a037d495f8d1eb4ba838b7312e5f6aedac02c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3949012 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
3 years ago
git_revision:febf962fa9e6f5cc5c4ce86e8dab6ff6d91088dc
wN2a62YXBByoREz7owfdlpk47efG7dq43ApwhSYY9IkC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-386
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
JYimpOASY1o5n0QFOHl6tXr0hTt4bq2Hj_xCRIg7GisC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
yDBZyIuv3tTScaAZM83Y7SKfJOyTVuQxIoXFug5NBSMC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
9AcRImmvWdcAeE3tcWcUDCvFYjrzyJf4aRcqcrbhdFAC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
AcC5M9REDrhAeytojQxZPabWNxyarmVM0BDaB-9pxfIC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
cE_eCkGez2WjVkQEYGh4HfOV9Cvb9K5kdBTcAL42WPAC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
4RUdTGJ4BISPHCYsi31bcOgn6lGy5stkRGE1Bl8KwKwC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
48mx-wNPfO91rYREi0nWKcYFl0C4SszBtPHyZtSy264C
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
LfQirdT5cXH93zHyv8HbsofJg0aOAfCK_jYDhnN-PBsC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
fbBX0YD1nYNJOIaH_vsj6LRdCV3n5RHIeYxLmpfnJzUC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
vYk_rhX2Am0Qn4IUlmYNtb-07HQUWqe6hKCGbWCP-b0C
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
7xKbphOmVOtt9ThAhpr6RQsv-WXqwR8vF0GdfO7JEIcC
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
wmf61CpSMIJR2n4VSm1KILDhspnYHfOtxIPKSwgc100C
[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][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
-AHhGb_RVVt0uqqiRYj4B05oOujzO-U6sHdD7Np_zL4C
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/prpc/windows-arm64
[auth][oob-deprecation]: Update CIPD entries for LUCI Auth. Fixed issue where token to paste was refreshing fast and made it difficult to copy in terminal emulators such as Alacritty and Konsole. Bug:1411481, 1406354 Change-Id: I260c18c4aca873530d7ead55ab8826b01edffd9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4231602 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Camilo Jacomet <cjacomet@google.com>
2 years ago
git_revision:fc9d7a3dff50d001c7c7dcf9f5f312be5d2d2ab2
7IGWu2KTPOqUOxVm7s0Movc33aBxFovLEypnnUWLueMC
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
5-hUyOPWTS9UgvmIRxVxryugPd3KV-mK3bxAKyr5nI8C
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
03FEaLHT7gyS0pLyUKkeG-3g1OoG1r6Jhy5XJBlRtdMC
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
yiCQiKIRfB53zA6tTXxmFirzARG3ef2h3sg__OtI4swC
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
15qmXIJPi0FFVF5vnXRKGG3dEp8vSeTkRhNL_fU8I6AC
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
j5I_w5uKSOcWny6HKagCCJpZzSc1l667D_56h18KLakC
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
L8mVB5ssIvYrb_KozCWS9LSRsC5ResHxFQPehZRs-YoC
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
3Y3LZ-cvipvsV7SNfadcB_Ybz8GHPwinEhtsVXWbUS0C
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
0a7NY9GP9W_Y11-Rhy0m-mJxpSFd58n4G-nrIEX1jz8C
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
vqe4jELNhIQtTWfbthMIRY0QmONNntMWbiy_tmWD8L0C
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
S8hcwM3btTqNtHelTViiitjhD6OMXALUdH9fBXB1UB0C
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
18B5zlu1mdeMOmjGz9W1EpiUmU-pUAlxQJsLE5RtANEC
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
K9fPJZ2FNIBIWH4q1WHn32fSXvmHUKe1dHQRLmD_5b8C
[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 -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
WCRPJYEBRgyXv5OLELeYsuBbgkflWIR0r3GXr5Fk6rkC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
infra/tools/rdb/windows-arm64
[ResultDB] Roll RDB CLI. Adds -sources, -sources-file, -inherit-sources options to `rdb stream`. Includes changes: https://chromium.googlesource.com/infra/luci/luci-go/+log/520840b412df..925188ce4861/resultdb/ BUG=b:274041961 TEST=None Change-Id: I0c4d08475cf61e94c858f7f33a58626079339d3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4421806 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com> Auto-Submit: Patrick Meiring <meiring@google.com>
2 years ago
git_revision:5111dcfc7b559e41a5256d3e7b04542eab70cb55
9belfdfNjXAva7w5Gbib08NbcH6v83Zd4x35Izcrnx8C