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

575 lines
19 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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
O6ChffXAafn2KNzLFlddCOEI-UPJ3Jg8BjNhoCcQRYUC
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
Ufsh7Be35nTha4HSYeWCX3aUdzDMUmj73-OwD41lscEC
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
5sj1Sz66UVmm-Q8wQH85flz6iuVP4kqsRrp_lMxLEhAC
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
S_VnGrTQIcCy5sRDLmURowwAzVJbPLTAtlJJzt4WSlMC
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
ztUE3gRvvhdBRP8XPcumLBctolAds5dSLNTmrEND9KUC
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
FVFoczG2ycsHVtWIyTf421eucm_Hxv77PGvyotracKwC
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
67A4bL-A-wCJ5zqxHheBPbi79TGRORMT5YIjpHVRfz4C
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
m5mIhauex3Alscr4wLmF4ouGlr7wi2X0QHcT3kCFzbgC
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
yzy_QfYoWJIXxnrgRKQxM0o54OrkfhCy63kVU5bC_isC
infra/chromeperf/pinpoint/linux-riscv64
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
re_gd_snZkAiqFjZ8L02IsN0P2EjqeqZ5gnXXgxLT4kC
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
1H-JYzH7DPNpCdr1zNKwtt0N6QnF2RadShCAKENp728C
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
SlPCkUcb3EIvgazMeZNGVgq84Qn8wodE1YEBbvgq08QC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
l4AehfpPb5LR_kqui-WCQX6sySymCuIdOLFFUTr1R7cC
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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
7lZuWtQZUHpdpKp_JPVx0F8vnkyAJiiFg7talumnf3IC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/chromeperf/pinpoint/windows-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
pJxQ0Hl-ATP8eyFijAa3xaYIms_8nfXxSX07XVxyKIwC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
5 years ago
infra/goma/client/linux-amd64
Update goma version to 262 Bug: b/301042082 Change-Id: I9cc5dd4291392c7ac561ce98d86e2e6379a1f703 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4895964 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Auto-Submit: Junji Watanabe <jwata@google.com> Commit-Queue: Junji Watanabe <jwata@google.com>
1 year ago
git_revision:603dfba63fe365a01879029588b48b6f122fe0b8
QZEdb4w286MM6sd9ALcXw36jDYQY9S1Vma5cfyQF8Y4C
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
5 years ago
infra/goma/client/mac-amd64
Update goma version to 262 Bug: b/301042082 Change-Id: I9cc5dd4291392c7ac561ce98d86e2e6379a1f703 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4895964 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Auto-Submit: Junji Watanabe <jwata@google.com> Commit-Queue: Junji Watanabe <jwata@google.com>
1 year ago
git_revision:603dfba63fe365a01879029588b48b6f122fe0b8
t2mJ5uhpan9AXxG0D-h5C5IOfz4ZUNjGV5UzsZnj6JUC
Roll out new goma client binary VERSION=216 Add mac-arm64 platform to provide goma client on fully supported platforms Bug: b/182514677, b/183118231 Change-Id: Iae7581883d403a1a28f7d0bb1b871c9cfd0f7e65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2816481 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@google.com> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
infra/goma/client/mac-arm64
Update goma version to 262 Bug: b/301042082 Change-Id: I9cc5dd4291392c7ac561ce98d86e2e6379a1f703 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4895964 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Auto-Submit: Junji Watanabe <jwata@google.com> Commit-Queue: Junji Watanabe <jwata@google.com>
1 year ago
git_revision:603dfba63fe365a01879029588b48b6f122fe0b8
sf__pdfvHmVZLaWZ9Px92vfrxu0Kc7z6YmwiiLe-wsYC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
5 years ago
infra/goma/client/windows-amd64
Update goma version to 262 Bug: b/301042082 Change-Id: I9cc5dd4291392c7ac561ce98d86e2e6379a1f703 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4895964 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Auto-Submit: Junji Watanabe <jwata@google.com> Commit-Queue: Junji Watanabe <jwata@google.com>
1 year ago
git_revision:603dfba63fe365a01879029588b48b6f122fe0b8
TsKkiGBqIo_4FByeFHO6k_8We2PKr4agbEcShhxHd6MC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
5 years ago
Reinstate reclient Adding back reclient to depot tools. This will allow it to be used for chromeos-chrome builds, and other packages in the future as well Bug: b/270080866, b/242680623 Change-Id: Ibb800a7c36f61312d540ee5595c585493e5e3578 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4273546 Commit-Queue: Eric Lok <lokeric@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
2 years ago
infra/rbe/client/linux-amd64
Update version of reclient Fixes issue where reclient erroneously shutdown during startup via bootstrap. BUG=b:269549741 TEST=Run bootstrap locally using the new version specified in this change. Change-Id: Ic443ba48d4d976a5341847bd7855e7d7fb63cc61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4445369 Commit-Queue: Eric Lok <lokeric@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Eric Lok <lokeric@google.com>
2 years ago
re_client_version:0.101.0.6210d0d-gomaip
QIkkdyLfCLyZpWdJoTC8EgbCT7QcUuClhWw4rL_wcuwC
Reinstate reclient Adding back reclient to depot tools. This will allow it to be used for chromeos-chrome builds, and other packages in the future as well Bug: b/270080866, b/242680623 Change-Id: Ibb800a7c36f61312d540ee5595c585493e5e3578 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4273546 Commit-Queue: Eric Lok <lokeric@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
2 years ago
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-386
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
Ux4Q6tJObegdVB5MqSh8LJpGWnu9cqIn-HtOp0ezMcsC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
jgHQrA1O_KeIeZrapv7qqQSg8zDhxIsLvBzlefQR7i0C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
f3e8h-H0Vcmf1q2h8ZU8uaFOLMynsXO-sT8Vh4YnrP8C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
uJMZWtgELQ3M9wmGlnfrSurz97s6nLn7RZ_67eomNEMC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
bz15HyWtbr9FfOcSbdIycfZwQ4raGTOz8YYYVgqEfUgC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
AY9g1G-O20n97t0JDV3VMm57SlIXSOWL3YbylcPFZiAC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
VNXQnjtwQtvGqXv565FGm4opICMl8mGztV1FcUWcYtAC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
FqGVGTZC1Xk0WvbcloEUBUitH9XeRUV9aAZVl7PJLrEC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
RAqrilNDHFNv2r6ULSOURtrzjR9xIvDRwCeLfs7FpqgC
infra/tools/bb/linux-riscv64
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
tikFb3PakpywYTd74SEkf7qMcF7Abgv3tOuN4F4qVvUC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
gcuW3uRaaLRt55shYABOyLUIH7IhpNDZsY_ys0UasQIC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
rXhLu5cttuMk2gsqR8tzmFzfiOjGYDYqAgq939GfwaAC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
jgZKPnui9YvS9B5muAG1P4KAeR-XaFYtVsIEYYotaz4C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
zDnQ2MSlSZ1IigumjoaNWwgUQXzNAGMICqYoNoAAgRcC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/bb/windows-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
lpA2xgV14QfKhPlfesgFtIQ6URbe7uMwDqEySMINQ7UC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
OVd6k2YpIu0Jf7UiSw9O07W8gFEp7BWrvLKaZ6Rnmf8C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
qOmF1ViCLapf-LosdVllLPbwrftHYpJ04EORumNRlOsC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
8jHKrCvEfHK9c0d3LB1EOYWYWdv6hcRbpxa1lFZlLJUC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
x3mu4_Y2laAtkMN8hkR-lmCk_WJpqXCdNdV916pwW-wC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
Xdaq7aQpclc7r7zvlz1yaOFUOkf6nuITqed6vvU6h-0C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
zJMLmmLAaV7useeDckDPpgI4C2n_sjtwNUuiWBznEYMC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
mvEwqmxiXHNemDl100QuoAnBjgTKYzDj2E50ta5vCEIC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
ujgT2OYyLf9WohkM7I9oU5EXNhbQPcRmIK276JuCvCoC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
SzJ7JolkTb4uczgjhrTJ0_N3mN7JxHgmoap6SloKJ-sC
infra/tools/dirmd/linux-riscv64
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
_IFyGhjJyXTp-Gly3KK2GosgAxvgzLCVDsvTyO188W8C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
7quwV9eLe7ApbDob85o5EtP8ADlcxDtIaogVlsPcRSQC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
IuxsSi2HAZ6n7KC-8f9GuEIOl23tfiRy_ZkhvnE6r_4C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
6z2f4Z_Fs52mXngIY0pFQVHKRsffIPfBfkAmwR2Ly2wC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
SaODdE7UtJOZffO6wsLT_g6eJ5vKjARH_6IkAR5nq0QC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/dirmd/windows-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
PmCbj9gf_CEHHzA1a5BA-FjIQr967oHZ4T6AB111siQC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-386
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
bItU6o-pcQcGlr_iExBuVYn8XNHYabtcuxyEh0QYas0C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
gYFNeAfhybbBS0WHac3cdfo9R4ThdVNqVcFw2LTyW-QC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
ad0WSrIrsC3mEztSSC5CDaLd1QzS8rzc7_HhY9Q4DSUC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
_N-w3kLenV5ibdp2ahjdMd5i5zaBJD7SR-B9PJ7M8NQC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
X9mNDThgzmpkngUo9I8HepJIJIS-2gAPjCuZ3dY1x8sC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
p7H2F9oktpS3dUtq4U1ggLCiKoAxeTv96_IyuavVkAwC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
XpO_JGXVpBZzcDhDThRT9TDrS1FtD3TB-psb8OoP1C0C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
Uv5W0qRRKJT0MsIXxjy7Bvh9TFx_0zgG21QqdUTmrHwC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
iA4CtM3ElULxax_xXXdtMIrMOOiCrRPiOmQx2kzZgsQC
infra/tools/luci-auth/linux-riscv64
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
UKU7cXl5fHVDZ1FQdEecr6fAliViJsteSpOZf3foNloC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
mMMavlRub12gKqn0rpT9dFQuVLOD5yphQuv8SbZ8e2UC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
UdNQrfV_v-Wa6pMYkuIbJNKMnRTIq-BhbPyA4IGBaHIC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
yEuESDIVsPTJEw8C79u0PbZ1Tf6SukVshSMgY4NRJ-QC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/windows-amd64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
Hsws1hpsh_jRxLWYT7UrN05UqmvUE0l-csfyF_wgQv0C
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/luci-auth/windows-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
gVGVpeHnRmY5YSLIaJwNs2Co26HANIHbV6EdeY7CnQwC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
mKlqOy3wIL4Dh3mOVyF4Mg8rVorsnx-0_e_zWvJwKWEC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
Yyz3AbrrB9BDfO7EdbKXH5_aurml9YlMXecObbHnGXMC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
HPSHfE-QrR2zlUtcEnKcMkPkUJI5avkW4M03E2mlV6UC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
rjgU7J5Vmji4uo8enSX2JKQF9LScZJ_gCgX4m1M0PJgC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
aGgX7FOv17sM0yR2ds19Uq1IbVZGkyGGBAnwm2Xuqe0C
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
vztzJ_QFd15f0iu-nCNImEHRv-x_fJtpWt8LN3yN49IC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
xkTDY3wcSK9nfNofqB3CZ7zk_SpO5VEt8NIsLROBtSIC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
zdSUjZkfvOvLQ-T2QJKJ0rxlpknUkCl4TV_B0NODRTYC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
C2bUsQ0imf7TdOQu-j8OaRyOMgioLotwqjOm5En4rDUC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
infra/tools/luci/led/linux-riscv64
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
GGt2ymz-ZOdQP7HIUmTsHomKyPvZGChqlNPeIAoiHr0C
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
6FSHZnWsPuDPvH9apYaJFyhMDB0-73C4fqypJ0vbTywC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
lyZ9GTvCr78UVFvnbKj4FOMjK71L3Q-F9GI42VZ0cBYC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
RbAmARVdrMhenUX8mfIjgSN-hny4wA4nnJYJ5yfzqnMC
[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] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
ns0JlDzm5mX8RWMI90mWAKhL2EP8xLXWUvnpTYrWjNgC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/luci/led/windows-arm64
[depot_tools] release led Change-Id: I1c80cf822751b48791b88a848aa1dde4a1631eef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5084558 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:2d4970c1db4df5cf1cc11355326729c3f8e37407
iFLwFAbHPlAUYS19AWmtUWkJUx0NoYN8MPjpBh0UWgsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-386
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
XimS5AqRd1GVnt5ulGPCxnq-9_Wc8QR74klusNRcZTkC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-amd64
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
DipTLgq76CIQIDSFI9qH0muk6d_9ZfY8aB2v7i_DgCcC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-arm64
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
TlMjUr7QZwAe03f3nLibDLDYgp9Or3haV3_mV1tQpI0C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-armv6l
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
kOIiAIzT_q1AysFuJwUJAlll8QFJiwEgWpbgJ6SiOscC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-mips64
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
XYntG_CdX-vdPX3tGa9mk--5h_TMeknZzfLClI-SKa4C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-mips64le
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
Z-5tAm543__VjTpNAMYdNx7mtT_319WpRQyoIT-dQz8C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-mipsle
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
Xhz4dWiR-A-g1o_5Le5KY88XJuTQDjPawNBOKtNuKs8C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-ppc64
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
0XDyjjg5sQIf_6V_vpivQqzKeoeafdJGI-fY0oSwVi8C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-ppc64le
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
nPH-v6714fduPS_2YujOGLMei4kfIpyFu5q_S7t7gdkC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
infra/tools/luci/lucicfg/linux-riscv64
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
UJPW2FT9JtgcNzyWu9edNTQPBoL8x0_NfPWkiYWKx1wC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-s390x
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
yl_Jvl6RClHVSOduKb87lOUvk4nyr1IqTe_RGzBzQH0C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/mac-amd64
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
XoShwFgZ6-xlss7b4uWvCy5ebHN7vDnFsO2N0oIO8WkC
[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
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
ouvtgdo5AEtB1iK12UniENtfsXEH1p7ie8c2ErgDO-MC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/windows-amd64
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
HPBG2KW0xBCIrjwS5szqa532-7PJiCtMdO8NQxHX3_0C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/luci/lucicfg/windows-arm64
New lucicfg version This change includes commit: luci: cq_tryjob_verifier: Add support for check_all_revision_kinds https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5057018 BUG=b:311018627 TEST=cipd ensure-file-resolve -ensure-file cipd_manifest.txt Change-Id: I68a694358edfcc91bf98554af56b224ae8d2131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5075457 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Ricardo Ribalda <ribalda@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
1 year ago
git_revision:25800cd69f747ec6a2fa13c1146a8807c6be6591
atjmgR-GF4czPvB-ke9w9ICK_HwFjlbfNgwdER2IwVwC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-386
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
Fcw5qURnzh21UHT-w3UtZPks5jofvq7BPVLg5cAerbMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-amd64
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
wcBGWJvGoGIDIIs-_02DGR-1pLEmM4X5ggRRnCExV90C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-arm64
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
EY9XfyyUfevSMHN-_CrgbxZCqKGh8o483WMsVnu_m00C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-armv6l
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
3f4lvih3rlq1-mSS899YQb2GdCUoGI1-bdxURJDH27cC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
QGEnt4YP9Wj-qbzdtpo6fjdXuhAjUQ1k08DYybPnrjwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64le
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
LqORhKXQ4LniQmVVPxUoDCWXpiAvhRU4wz9FzKv3L_QC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mipsle
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
PI2snmergXBHX23rJykg7pntmJgsAINglAMdal-sXwcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
Nd6HeQmM-sRJNEy_iJlxzhQR5Xhq15rIomNx1ntcr2gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64le
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
bTeLoN_efpjdYrnap9B1L0neK8ygHvQ57pi31zwu1ssC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
infra/tools/luci/vpython/linux-riscv64
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
tyV0T9ZiURRVydLsZabbAwICd7lliO_dWlG82XKVftIC
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year 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-s390x
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
o0Lc91qZidXck4o4mSLkkv_caefRaYAZtqWrFbSyjl4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/mac-amd64
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
UfManOOg8GZIFaF-6j_pGM6g0vTLynELKdkPiXd6OIoC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/vpython/mac-arm64
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
3-bLMiGRYwxhA28AxnelDY9nxfSeaM8I_mdnkywshV4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/windows-amd64
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
nclbAgZdQDDMI9gTrfbl6JsvhCLPLZiQ2_zvNPwgTAQC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/luci/vpython/windows-arm64
Revert "New vpython to depot_tools." This reverts commit 9e5fc28b6b27ad4ffb4c3ddc66388e53e4f0f5b0. Reason for revert: crbug.com/1506442 Original change's description: > New vpython to depot_tools. > > This change includes commits: > 00e23cbde55df05e0e42f7a574c79ff8bcf589c4 vpython: match tag before verify > > Bug:1501997 > Change-Id: Ibabde88c588a830707bf14be7e2998fa4b4152fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5065788 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chenlin Fan <fancl@chromium.org> Bug: 1501997 Change-Id: I7de1b42f2dbd661cf05371572be3d5e1e9785680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5091007 Reviewed-by: Brian Ryner <bryner@google.com> Commit-Queue: Chenlin Fan <fancl@chromium.org>
1 year ago
git_revision:7c18303a74d8a6ae4bb3aae9de8f659cc8a6c571
mNrlcixOu81hisSF3ecC-SJeEhbtudLtsdLA9tX5nJ4C
[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 Added more functionality to support Xcode15 upload/download Bug: 1472416 Change-Id: I942abdcfd9fbdc012ff2adf042b41d173722deb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4833277 Commit-Queue: Yue She <yueshe@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:05fe195bf77656743f3daa99d463a794260b429b
1NcxKh1FggudsW2m-k6yEZ_Me2sObodtag7de6Z_D6AC
[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 Added more functionality to support Xcode15 upload/download Bug: 1472416 Change-Id: I942abdcfd9fbdc012ff2adf042b41d173722deb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4833277 Commit-Queue: Yue She <yueshe@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:05fe195bf77656743f3daa99d463a794260b429b
maNrol9N_NRlbWSCnjpV7aQMBfxoBEhtoCeCW6ORpOAC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
SLJcDJyN1t5BR8szKiRDw39W9YOun1Bfzig0uBImW0YC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
A882JTDDbItEuRH8t9gFx9Pq8uOfpIMl5eAim3Ze_oQC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
BABpEN_EmifauxYOkiOpVttYeatWaPnSry7RmR28a0gC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
cyHtQ7iqXUDicPoBp1_3MeqzHymU2gSq1L0HUAFzp6IC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
tI3j6aBFXgzODwi6b6eJmjSCgfcCqBYvRwjlUpS4WrAC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
YSfkEbA1Xx6nxGqw-VQtIcznnDk1ren9NWl47YgieycC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
eP9TrN_x5dtgf5lzizrs7tH3F4Ha0nkCxO4RBMazKLoC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
6bgBO5Snel2Gh_kXd0Xmm8LjLNKCwyLz-b8Jk0z_jYcC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
Z3f6vtVnTsLD_Az1zZlyh-fxZf5Ktiq_zQSrZNPudaEC
infra/tools/prpc/linux-riscv64
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
ViGe-nRNBp3uX-4_yv-_L2bSWr3_PLtvExEm9ZCdbQUC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
GI-ec477TiZj_qKq8TnaTQHTd7mNg1HIa6sRsiKvT98C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
L5auRzn91XQg-yZgF1rcKgDNNFoyXRgcrBcT8CyFPxwC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
8BYgb-Cf84StNfoaBYY4ewI4U8N1db-xOY72PqXUuJkC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
yyuRRM4hxE92TMqkRcb_kteWfro6Plt3u7opJFufS68C
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/prpc/windows-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
iFQvbmYSkL_IlmJkH5P21k3_-xKFRe4pshtZbH-k7dsC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
mLiDmwbha_MH8XWgFXtQ4dlbogO0tjWufGuETWClG-EC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
k-F6xShMQQJB2gaVKozbveB3f-t7a7I9RWQcGoOc0foC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
vdq4SBVIVvGLkD7GU-v5xjHa1YEsGriW64sZ_FRZ9QYC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
83RyNBptVL5TPkxDYfHKxARbpT0lwLAvppac4S7j0fcC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
VUl3gkJdtMuri51iU06ouWgiIz7v3CFMmcK8Mbv-Qb4C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
aE1ZNZAZSiBNrro3zBiZFmh7uQu0x5Bmto9ARlxwiS8C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
B_zptuukwUhrh75wdG9YKZDIQfIKY7U3NRB_fFlwd6sC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
KVGfcNXXLrvCVg0IEpoa3PqK0H7QSxCnEF0sEZ_n7OgC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
IVcXYvqtgAuajLw_3v0qNJYA-45rkqTVMmlnlroeNUgC
infra/tools/rdb/linux-riscv64
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
kkuR8eostloaZWZxW_ZCvE7NqFpy4cRI3qANNMt3vN0C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
CNuMnHrywkVMFGXHHnFAIrAN5t_Hn9f61Ec2R7T4zYIC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
jaJcev-GBsW7yERbmxsHvpiLQR8xqF6J3nDoMO8-OOIC
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
RCd-hnxzAuxIWNzzzlxkKjwUvKh5YrzshQoPjYeEBR4C
[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
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
zimOP-6pumgbQS5ZyBiyO28rsWIz3gwuV2vjAkxIBUkC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/rdb/windows-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
RRbrrCeUvNPrDTOQOHWWusLMD7k3s_wxGSG-7ifggJQC