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

499 lines
16 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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
L6jCRyWV6p_okvpjElrvR6wz7NwzYfgyTGe-DEokFE4C
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
xyJl1pI8wxbO_lO4ueqRwY29Z0Htpp84t_FyJk0wnqAC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
Lkze5BLDmLK0sCQhWfn9axnjgY0phxTPaJBXMut0StIC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
y4rKFy1ux70B0hDg-VlIOfFwqMXtZ5SIR6ZdjMu82TcC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
jqCV9k4Xnji8oAM8IusHRgw4QNpYedvnSa9v1YB8YTUC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
GMLESQzJkGDy7qj4B5PIv0MEV5Cfp5FNu9UTeQorTQIC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
h3XDWyG_Z9WpPbGZTQzs9JN0SVgGqm3QJeG9LcsTwJQC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
AmVdLvtg-HLNhPcz7O4mX_iz7-c0HhQmntHm1WQw6oUC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
ZMZBqoLHsyj2UHUMN10o__WKzmYgprsxs6FM2noeMZwC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
giu0eWLsmIY1YxM5L_LRgdQdrN9Fj6FQzxY2ATIsYDEC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
igT4IYGSiVRwo8q9BGJEWFJSjZnCOTRv3rKGG3nnCz4C
[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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
aORUPnDHf9MtlSuBJAMlFdviAr-rCWpg4gnNyHyLPDcC
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
Update Pinpoint CLI to add job prioritization Bug:1241906 Change-Id: I8698621b1c80247a5387f0914683b90c75ce4c30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3251540 Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Ryan Heise <heiserya@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a424d157d4b2c0d0115d10a374148d5ea4149117
LbPyRzGEejdVHtxjMc_u76FuTFul6MkA1fnnT1PCDMUC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/linux-amd64
Roll out new goma client binary VERSION=238 Bug: b/206331104 Change-Id: I0ad8ee3a7f8df19f0414a174d02e95fffc3105d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3287049 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
git_revision:5a9919a38b56bd73e5f5f8e45a78fe87ef841368
zvT7yUiq8BbBADixPiObkkQyUaBTdhbYrmvBbhywb04C
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/mac-amd64
Roll out new goma client binary VERSION=238 Bug: b/206331104 Change-Id: I0ad8ee3a7f8df19f0414a174d02e95fffc3105d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3287049 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
git_revision:5a9919a38b56bd73e5f5f8e45a78fe87ef841368
SO6KrLXeOF0NTGVobWpeC6tDqcJksTRYf0Z8b-szFBgC
Roll out new goma client binary VERSION=216 Add mac-arm64 platform to provide goma client on fully supported platforms Bug: b/182514677, b/183118231 Change-Id: Iae7581883d403a1a28f7d0bb1b871c9cfd0f7e65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2816481 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@google.com> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
infra/goma/client/mac-arm64
Roll out new goma client binary VERSION=238 Bug: b/206331104 Change-Id: I0ad8ee3a7f8df19f0414a174d02e95fffc3105d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3287049 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
git_revision:5a9919a38b56bd73e5f5f8e45a78fe87ef841368
1sZZDp7SZ40TawPrGPVfpAuUsjobRTotRb-CWC8JV4MC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/windows-amd64
Roll out new goma client binary VERSION=238 Bug: b/206331104 Change-Id: I0ad8ee3a7f8df19f0414a174d02e95fffc3105d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3287049 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
git_revision:5a9919a38b56bd73e5f5f8e45a78fe87ef841368
L8GLYuXk_OC2zwr8IpivSkVSPxpsBxIG49mDECl_PwEC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-386
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
nfuWcouxLXZ_QVTBQzTYeBclxdmbEP978PMBcu6D2YEC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
ukfK0rEDJnHssVOzMJQjXyJ_wMGaonJw_jDB_xP1HsYC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
FwjZxkgPOcSr4yUSJvuAx2dLI967HjkYL392NmQcLKQC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
Ge7N8w-FrbE4TZCDfg53f-ZvqnEIo-pOjZYG5QrZGeEC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
DzcJgGarfTYpoV8_i6w2857RVQJtC802WovJk6QDonUC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
b-ei3R_nxMcOWg2pzGYXSFA0S6rZXcBW8wWELConZ0IC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
9k95gMDhSZlc8m754MyTM5EF25GR8GxUcrEhTjzbS0UC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
bJg0fWoBWyWkgR2xy6kPAz_LhcQ9wCcAEdjbESSnRZ0C
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
7RJpQpPnhYsZGqyKN1NK4hQST2HO_X9qY6AVvQD1B6UC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
lMzl9b9o_T9HwNoVIDV_yT-39D7iot0OTFLhgScQ7_sC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
BGLhCtjzuucq3hS6L7Cb8WU-1r90a9RzY-gzAcpEJcEC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
DC9rpnYPFvhpYsR5duBtPYfpNattWUfpcA4h9sxanHcC
[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
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
B__VpnkTIRXnZyy1hueecfk78ZCZEBIQV2bgMn-ZIooC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
nax9jbdWIBujTifdWmU0juFen2IpIMg8JvK6jpnI-T0C
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
vhOUATHupnpNWDxCO-KnGXbnd7BQcQOgzfBw9GMXcDMC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
x7TBEpsXTTvo7mHxCXdnq2QEZWGcXr4t1Md8SfN_df8C
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
iAKjZ3USWP35fxTfIyJ59TzlOiLfutX6DpOH1B_27kQC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
ZC863vR147-KZxL6wmzoXyTkQm_v-dQulZqfD2PTj1EC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
wA3d5LMTgsnfmhg656IUsqcUX1DbvN1j1XHAr_Pg5XAC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
xO0fifz05omxMMW07DQeUUvMg1jds-SUJPifQ0MovgAC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
fayMG6ngM8URXVYTLKSv8-lu5CmCW0AFHaXLX5Su8ZYC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
qAJxau3m9DZnh_7EhcbA-oUs0GF3CJWhk5IoBV6XHBQC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
Pdd9gyO_iWfNr4YNP8t-nc95PeC7J0W2PhHl7YxaZqQC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
8PUAR4JvhNqZTo5dQFB3diF3mWMkezVBxIaUn7WKnkQC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
tJV6CnIUm6n8CmBbq9Xa0nheJaZj-COFUrBxAeSxARQC
[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 dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/3198310 Bug: 1223076 Change-Id: Ic85baf299ebbba60c46507b400ed04a45742e0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3198031 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:01089e44c7beb1c1f47c79b17b87972ab01be311
yGvDt2Bwge3XY2xS2s4O9AOBjJsvukz4da1cjCIeqGcC
[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
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
eP17h5YJMrU6hWBOvjZxWCz5h9SgkkW-vVF7W-L9qwIC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
Xf6nFp5RbFKQLUk7d3O5LKPmmdnAF8NU4NsoO0QGP1UC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
owOKUdyWr11KyfuCRigGRsBM7uPnOMVrH_WOMYYCGJYC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
iZa8O1smpKFTta3pQVz9TaIOlRIu31V4QPgGbIVkCgYC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
s6dXt6MAJ8kreqm79HyghgHg9mk93u8ju303d1RIZ4cC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
K2S9QpIR4701H7N2E6Fm9iGCOg8hwa3mY51S1CmrwdEC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
0jLzmuxOsRVyYofMKQfgivPZOtxsXv0Slcr1dRU78UgC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
7SK4rFVEOeA4CqHD0mKebTOCx7viE-dJMakFqE6W6BsC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
ZruNFqBhC_reTL2dw3wf-t17dc_sPZJ_733R6BLBvMsC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
8q6NmriGR1GiT9e-UlHeau2VMkcN0UYumU8AVDLIsZMC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
pxk-T_GADDuTTtmbUsK3TlMHbsMD8jb5Dt383XPmeeYC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
cR0PKTchP7f5iIXZdCSffnp_p1_ySee-16Gg56qhxqIC
[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
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
McEKBb2FM2gMj1og3guOfA_jd690eGivhdSbKP90ruwC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
Y-0vmWcNr7P6UfpRPxXit1l2ys07CkzVU7q_x0HTzIwC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
jpfC97yzRs1SPKEts_HI_3Eqg8nlwxCT77Wv7h_FBdwC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
bJJUNZGqTom4kg4MsBxrd5UmyAiICMq3VPGnctWSBOEC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
zTX24vs6Rnb-81oPV1cGSBUEeY7s0y8dauQtNv5XKP4C
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
7eHkogZiPl4hwIFmA5vcorVMUBTwzDVSI24JHcBFPEEC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
Ks1kbFNfOlo9u9dFZzExLAx8WZ5yWCfful0yh0WB50YC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
bFwYaZOtsXm4kuDfxN3pkNxlmiH41c70gdlhRsCmTpwC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
kc8t0JeWXf0L87DoUlkXJ5vOFdxfH3kFALW831FPBBQC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
Kb1jnsDV7hyCfW6bvkBruHhnoEMCaMRNFi33HWnx6RwC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
ke0SmDvpSLmpL2Ojc6pd6WKOUOLyK3VL8HOFmHASo6EC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
bwr9StjtYguI5timSSByCncYeG8yxV2CQKQE9wU2CDsC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
Y-6b6N-4_p_c5f4dNrRHgBjjbcKaOlH0MF5SHDrCpHgC
[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
[led] Roll led to always use realms in `led launch`. R=chanli, vadimsh Bug: 1254504 Change-Id: I1cf3699b44604bf6d3b6567da72bf7207cc0193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3260772 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:2b6c41a617ae191ad5341683570f0a199b798ec5
BwV44uIHSy7VllybQt13umzdO4l8AEI4DVS9nxZ0GCoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-386
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
GcI8zCtYfbdkm8IswYVWed8BjoRgQTJc5UvYZqdcHOQC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-amd64
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
pCuBmYdlnGC5rJ-Zr_FsEpKplNnq4b-AewitmtadmNMC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-arm64
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
Vh7t0sV5qulJc1Dlu-4OQLTAncq8udbrsLZpQv-pBWcC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-armv6l
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
cbC73djIwGuUMZgvxXc-bW3wFPp3ma7i1W3aI61NiL4C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
d4m4cjYFc_UlZGoPQt42j2NcIOAF1JVjxCdJIvY9UeYC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64le
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
w-ogrNveZTxR28w0AwCAFwiErnV1pBzR37Y6HfH_aiEC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mipsle
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
yyO6MSkVXzlDGL69pnq1U3OveBIScraHBfRPVlt7OjsC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
MAc9kWl11mNi-AOm20w-zr8hwB49dxH1NcSJLmmapfEC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64le
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
9elXOjcXOGTWoCgLcNnkg2ksJ9DH-T7eReM1YTBsd7kC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-s390x
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
8f39Ub7Ah4U_5Ikc8Rrw5M2IX49xZZdjQAc-Zuo9JXkC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/mac-amd64
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
ZYyFERWnkqFW225eJdBivZA-ZujOzPMCqEjaiS0w5aYC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/lucicfg/mac-arm64
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
yan4uSDs-wHhfW2E-P9Bx8-VyRHI9GBkALbwmTN-S38C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/windows-amd64
[lucicfg] Update to 1.30.1 0fb9c1a98 [lucicfg] Add recipe kwarg to turn on python3 mode. 76addbdc5 [lucicfg] Mark swarming_tags arg as deprecated e4a84dce9 [lucicfg] remove the deprecated milo bug template API R=vadimsh Bug: 942720 Change-Id: I20004c5b0f9af465e3994f02098d6deedc711bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3258487 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:735bda925c07e16382897e9786a3761b66eb6998
jrRLTDeKkCb7oRLDi3t8aGqvoLU3Uo5RDaZdqYEluVgC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
PxTcPoff_ueIarMQpyMpMV6FhqrMsymxJuXfMWFF-8EC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
g985OiQROdCNDoMO-myGkRJgAPiQQ0Z6M0jJPkr2J4EC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
sNV48XgtWRuC3ve3fyvUvyZI_9PbypH1i6DCBOZtekoC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
eqZQiVei5_cKxV7aPFM06cQ-HzIh5gunnIhr86tGkQkC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
YcjzPIDuxStXgrglITDN3oukz4MytvZBI8QqUpltMV4C
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
l-p9wuRDnV3yMS0Q_SEICr9vSuppKw-ZDkIo30iqN-AC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
0h1jmjeUVIZFtowMtYgc_bXSus9Ut2KE8gB4cCfr-oMC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
pCDq8o7gp_eqCkdVcdZSMwyB7d3SJWvIHi81r8dZpPAC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
DkJVdlrwLADsvHOlpG1Ie6FMzcHUOrMXYst8UczSrjEC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
Te5Fm1vbxqqMVbdJOGeneYddHhW3WBELPCMnHIYEO_kC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
L9r4L_GDqlG7WyocecGQJ8dKcICcs7wioh8Z7DkN2qcC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
PUxxUy9m3Hv-414jMEtSfZ_Rfc7YCMoto07d99yPVTMC
[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
New vpython to depot_tools. Notable changes: - Fix for missing runtime DLLs on Windows - Enables native Mac ARM64 wheel support - Startup performance improvements - Fixes to spec validation for python 3 Bug: 1237202, 1103275, 1219868 Change-Id: I9beeb9dc5e82630d3cc6369a501fa63b11d1321d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3158553 Commit-Queue: Brian Ryner <bryner@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:a058ec28ee4f76d255fdc3e1676a8eb2e39479b6
PQQPGKh-DN_7UMGw0WzvCuznmCm-8o2Up1OomFWVo38C
[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 The roll in depot_tools enables new features of uploading iOS runtimes to separate packages, etc, for human users using the tool to upload Xcode. Bug: 1191260 Change-Id: Id6334afd599c9345f05c7fefbd8407f3bc3f8124 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2918693 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
4 years ago
git_revision:723fc1a6c8cdf2631a57851f5610e598db0c1de1
2ozLryqklxu4fc7KZr_EqEpL66z0G0moWJef2qnPXXwC
[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 The roll in depot_tools enables new features of uploading iOS runtimes to separate packages, etc, for human users using the tool to upload Xcode. Bug: 1191260 Change-Id: Id6334afd599c9345f05c7fefbd8407f3bc3f8124 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2918693 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
4 years ago
git_revision:723fc1a6c8cdf2631a57851f5610e598db0c1de1
1VL13oNQ2PA-Ez2iYTQOWHFcXwA9UD_nhKdhqXsJw-MC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
0jh5WJiKY3YuD_Jb8PqwvoEpkIErWxDjPK1zHJt7AWsC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
ifuMgrBw52FZoNeCoOOBKJnEOVZissbo16oyfdNNFR4C
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
37GBPQH01OFQ_mNexmZL4JXvTJrJZ6lupI2oipo7NygC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
p5RXqsNOyauZgCE7fUiaJjjvfiyOaduXWxsPi79jSusC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
5vO0g5QLGwZINTFQjnhKEEMDTaQ2geUUP16w3T7icicC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
FV4lcmPr2Y3qx5dC85IxvN6j26tgBTIZY3KL3OO6ggQC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
ZLw57efe_OTsHW_Sl5W2tK29zOx2xEi7m6XqQVEAS6EC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
1KLg18xHw43xbVYfPMPXBhqANzzRwP3aYRl0wi3qohIC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
hKB-qdoedy6YFlpMY_B2sNmhdoJzQbcRRU-ivr_nPZsC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
Z8errTmVek00stSE8njJ4agFHThZWdziTgN5qpNDFbcC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
SyQL0RzHkWotXKicxXx49tVIBYW56N-NeDSB046eXwkC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
M2wFOESsz-1S_BtbL2dKzUhxAspQa1OolA-J954ggjQC
[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
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
pZ4PpzsgPaEjhtfUbbynrRQQ6e7zNBnEWnKn6aupqyQC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
R7rEdwhM6KMO-bLlPQscu7P-UVqM3xlumqr9vvi3EncC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
y2RwvR_NY-gITzTR4HD01OXx20yD4qthXYST6eubEJYC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
Ba1muEd9VQoVbSBKpj4qh0M0M5uUsdBDFJZvq-RN-OwC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
ZJjdiNekm3ZN7V3I3YYJFuBJ_Pvy_j3o-wQCq4UwqDgC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
pHLG131TuW_iIybx5TltE1FQStEUtt7DdOhu9cn9rDQC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
eypMmgNkdyyfCrOamDQZAaLDqoUAEwFTL_aDe4iiP6sC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
azuk1r35DtMtfgqtBwlFoMbW3tDMKMo_em_Ays7qqNMC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
tu1H4eI7cCmDZT1ONDYUu2ARmSaqvL17yi9LUfBxDXwC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
JNIGWz1RIdu3K4Db5QvXFB1lCLRBD-fKhEyaz68xLQMC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
VGuoL235VqWEL1P2enaNz8fe-T_hbNU5qLY5VsVKmr0C
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
Y_H0AySu8O5FLpB9t8vqYAFtrkwRRqG7urrjmRzbyf8C
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
ylQe7rPPYIn7yQ2x1NwlU55DH5Karq7v7-XNPxjP_6QC
[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
[depot_tools] roll rdb to 2be056d0 To rollout package: https://chrome-infra-packages.appspot.com/p/infra/tools/rdb/linux-amd64/+/git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833 To include change: https://chromium.googlesource.com/infra/infra.git/+/671710b97226806cb2fd20eb1fcb5f88fba27bd0 BUG=chromium:1226947 TEST=None Change-Id: If775f6f507f3863d1bdfa5df6db9048a3f276e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3055340 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Patrick Meiring <meiring@google.com>
4 years ago
git_revision:2be056d01d3f8bab07915a1c2eca04f1937ad833
9r6QPQmkPAbvoCEAADMFk0OBP6kUSicxFQYgJMbUlysC