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

519 lines
17 KiB
Plaintext
Raw Normal View History Unescape Escape

[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
# This file is auto-generated by 'cipd ensure-file-resolve'.
# Do not modify manually. All changes will be overwritten.
Add crosjobs to cipd_manifest BUG=chromium:973247 Change-Id: I8be6386fc3ab9ce6e8d9558862dfd0a7c74a5e6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1743018 Commit-Queue: Yaakov Shaul <yshaul@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
6 years ago
chromiumos/infra/crosjobs/linux-amd64
git_revision:ed616d595eb7241d39d34907050d2949121d6ae8
_vAeU0Q9lAxn933K8vDhwGK40zKVvV-yXGpIy43ATXAC
Add ninja to cipd_manifest Currently, the ninja binaries in depot_tools are committed to the repo directly. This CL installs CIPD ninja packages to replace them. Switching to CIPD ninja will be done in the next CL. Also, see the performance comparison and CIPD packages in the comments below. https://crbug.com/931218#c84 https://crbug.com/931218#c86 Bug: 931218 Change-Id: I44d5e9ea1447588b32a10db20cfba088dd748f48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3674981 Commit-Queue: Junji Watanabe <jwata@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org>
3 years ago
infra/3pp/tools/ninja/linux-amd64
version:2@1.8.2.chromium.3
PUvdixKxFO_KVk9d6WFpXLVDMM0MHv86jyyySTMQ7KIC
infra/3pp/tools/ninja/mac-amd64
version:2@1.8.2.chromium.3
w-R-1UrTQJ2UPgSjcqXMayjE6pf76XpXE434rOY1EC8C
infra/3pp/tools/ninja/mac-arm64
version:2@1.8.2.chromium.3
nVO-Kzyky9nfG4pRb3Qo7KdxyoEXjdwuOhVwy-h0rbMC
infra/3pp/tools/ninja/windows-amd64
version:2@1.8.2.chromium.3
HLdWFKyFMpFQO3VFSps1gevQGwY95hEBUFblIfDux5QC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-386
Update Pinpoint CLI for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
maajkZJ8vTrebCH20SasSCaQ4XnSSudDFSXEaY3CBYQC
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
iaUmYzrk8aiprULbAf8NdCiYVp_8iitWUjYPg_41Nk4C
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
6evc6slMI_Arj0BaVb-_p2_E1jPqArBmXlssHXjHqKkC
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
Cd6PDAsOfHhYMDEkjRwDClbFzpA0Qmr_KWMIhXI1N0sC
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
GakP5Gtq9WtWDZ720XBuM3_XlOa0ENY56aCkJGGa7LcC
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
neRhfr_N1giqM5vbgM7gadyznUIxrEeh1JdkLdViOa8C
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
3dhM1zF2m6y606OSx5X8wyqj0CMpbem6GAENbx9Ro20C
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
MGe3qRMljGY1Y8J7UyCJo4fdoHAabp8NiluBSXlclC0C
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
ayuIE_2DcoLk5C85Pq6iQNk-ip-WadIhxnmrNKy6xUoC
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
cX25NHyRWRYdUab3B2274u5xtpfgedsSwvzcoNShpgAC
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
eZMujRaZvGl7wBhQfUEuoihWWt2rxx9bPhiENFmoYzsC
[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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
c2KZT-7q8LLDNEdYbqWF33FfXI5PrI8v9Ly92_rRCVkC
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 for Octopus Bug:1159092 Change-Id: I626b7faa21f073030594a82fd98f510177e2f388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3760945 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Ryan Heise <heiserya@google.com> Commit-Queue: Ryan Heise <heiserya@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:53d72e5099bc6f080370ae5f23560383027b947f
zvmJOlA_DT_jJLVhgrxh2WjdXeHxrS6CoZaqk8MBprUC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/linux-amd64
Update Goma client Release notes: https://g3doc.corp.google.com/devtools/goma/g3doc/client-release-notes/2022/2022-10-12-version-253.md?cl=head Bug: b:245256182 Change-Id: Id7fa14832edfc24c0890824bebdd136804e79105 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3947889 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Richard Wang <richardwa@google.com>
3 years ago
git_revision:b518ab221d24628f2d5867be9ca66aa12cbfffd6
h8qmkc_NKK-EJK1Q7eX4WEFYLkIho1Yva3s4he82MqEC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/mac-amd64
Update Goma client Release notes: https://g3doc.corp.google.com/devtools/goma/g3doc/client-release-notes/2022/2022-10-12-version-253.md?cl=head Bug: b:245256182 Change-Id: Id7fa14832edfc24c0890824bebdd136804e79105 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3947889 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Richard Wang <richardwa@google.com>
3 years ago
git_revision:b518ab221d24628f2d5867be9ca66aa12cbfffd6
QbQa5hpHCCkjinoaFiu-HlMWZ7G0jqy0RNkC5AoCUbMC
Roll out new goma client binary VERSION=216 Add mac-arm64 platform to provide goma client on fully supported platforms Bug: b/182514677, b/183118231 Change-Id: Iae7581883d403a1a28f7d0bb1b871c9cfd0f7e65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2816481 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@google.com> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
infra/goma/client/mac-arm64
Update Goma client Release notes: https://g3doc.corp.google.com/devtools/goma/g3doc/client-release-notes/2022/2022-10-12-version-253.md?cl=head Bug: b:245256182 Change-Id: Id7fa14832edfc24c0890824bebdd136804e79105 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3947889 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Richard Wang <richardwa@google.com>
3 years ago
git_revision:b518ab221d24628f2d5867be9ca66aa12cbfffd6
mGcUWArYekIW_cUQxklBKL5LL28BJlChnH9drK2jdRsC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/windows-amd64
Update Goma client Release notes: https://g3doc.corp.google.com/devtools/goma/g3doc/client-release-notes/2022/2022-10-12-version-253.md?cl=head Bug: b:245256182 Change-Id: Id7fa14832edfc24c0890824bebdd136804e79105 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3947889 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Richard Wang <richardwa@google.com>
3 years ago
git_revision:b518ab221d24628f2d5867be9ca66aa12cbfffd6
JakWdTGkWDRR4sr95vIV8UIsWFPX7k0cBA3jUe45oKoC
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
add reclient for ChromeOS This will be used in ChromeOS build_packages. Bug: b/242680623, b/203606263 Change-Id: I3eedec7b245405c24091db43a450181a270d1305 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3833266 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
3 years ago
infra/rbe/client/linux-amd64
update reclient This is to import the same reclient with chromium having LTO support for ChromeOS. https://source.chromium.org/chromium/chromium/src/+/main:DEPS;l=288;drc=83f1b84510481f751b5a6e42300bcb337a0024a9 Bug: b/203606263 Change-Id: I240995f976fb569d223ec17a3b2afbd391a88170 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3937853 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
3 years ago
re_client_version:0.78.0.6f1e751-gomaip
h2KxtJM_aWr-IZHfFZptqCDmg0FVv6weMneXQT5uKaIC
add reclient for ChromeOS This will be used in ChromeOS build_packages. Bug: b/242680623, b/203606263 Change-Id: I3eedec7b245405c24091db43a450181a270d1305 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3833266 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
3 years ago
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-386
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
FuKBzmPXerJeqd9oH8r9iOEb8NW5cz8r8-lLuIxN8rUC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-amd64
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
OpjNa-duKhW38bq0Vu_NcCy1DqGDb5coO1vPgR0avOoC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-arm64
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
QAsGjkiahaGY-kbi1XqIIQ5SJfTDKYRNPp79wmi4vyoC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-armv6l
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
MrSQNy7w2fEifz92h8KKmllvCApTd6mi6-_x_OkssIoC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-mips64
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
h8SKlQVDCbAX3fZDVpPbix18ZdmVM-lAiOzgxDBerQEC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-mips64le
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
2Q8AlJqVc_ou0zG2A064WveLAfKDVVdfT0DoPrPIZN4C
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-mipsle
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
37ivCgbwrCyaB4ZyxIvJ34kpm8jd8Ra95tysGfqirG8C
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-ppc64
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
fgkRGxwKqsoxeafPO4dt3UXiBzPJ3YoG_ujHU7jhOaUC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-ppc64le
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
zt4Tlk9IH-YGluYH0WQV-aGQt620TJcvMvSni8qZltMC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-s390x
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
U1I5bKqtUM6hQCK5UNA-M1nD3ZN5-NtWV5oPw2PL32kC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/mac-amd64
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
emCk2FLSkKYJerQzyBCGAXQ4PELVTGQKcNgN-qQJaPoC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/bb/mac-arm64
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
kM7e6ixtnRY-wG3xnBqkp2Vj5g9iKzoX_fTvCHM5mKgC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/windows-amd64
[depot_tools] roll bb To release https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3825181 Bug:1347622 Change-Id: Ib5daf9fa35b764b6a3b37e36c7daa8fd94625817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3825397 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
3 years ago
git_revision:a6af4ce16f5006eae354d82017564141476c6fe7
xf3g1mDRR1hFCJAuMFNCaFPCFyadsbdsrkZKshdHr8IC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-386
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
FzZH22AH1jY8YMtpr4xxzaiyKlVSmB93k87GoRyHbwIC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-amd64
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
mgyvbEbfnuD8b5Ei7jz1Pf_fw3jkn72uDNbHJcN5p_cC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-arm64
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
93rPIc9vjyLIfweB2gMRsz9tHdhDa3801d-6zR-NzcwC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-armv6l
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
PMbw5W8EuosPadSeTJlmRR4NRNY8EtN3NP3OhnTqEj8C
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-mips64
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
StcCOsX8bhHer4kntzJV1FD2-2LonHAyXeUz5OqrpYsC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-mips64le
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
Nj166cpcXv-5QUNbzy691eJSS3oa9pNY8VzZsbMS1KcC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-mipsle
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
vABtBUykbL3DMwsaYMgH1xzEN1ujFF0sMssiMWBAe6sC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-ppc64
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
GxJYpr_1ya1Nkn5dJhy4zkgMw5NmQGn2Idin748a2-UC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-ppc64le
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
dOqyFbWkOvrZgC_wF6WiAtN-MQfyZdmRWOESIay5meYC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-s390x
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
QHx2WUjN_kCTL3le2B_5ecI37ar_1HUjGqySLvTyAYUC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/mac-amd64
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
EEsFiejTvqWlWDYq8clSIdDp7LBGmWcdQeAhoSLo3iUC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/dirmd/mac-arm64
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
CnACaN8yKdwP3d_YTEqEbDTbf2fOxIG9unrm86E1WXoC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/windows-amd64
[depot_tools] roll dirmd To release https://chromium-review.googlesource.com/c/infra/infra/+/3827304 Bug: 1349169 Change-Id: If1ac56926bf97c1ce3b373d67e077d120d78fbbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3828041 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:6ccfc187ae31591c9ce32acb35334062530c5333
1JotooPrgFV1R52tL11-JpaBaJdFLYBx9mRlTUuhTU0C
[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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
mhgtN7wbShyq_owS2rD8VM-DLkESEmcHnbpM318Rj5cC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
BPjp2aKbWJHc-WFnIVFKS92qzeg_4z59wcMvvlIZhYQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
ftSZERhNyR2DmnWA3vyA35BpdWNu4Nldj8t48IzTINMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
b3SaZ3V8bIsi1hlgZw2W50SC8u0UnzBqppvcSNLunvMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
-NtoaeAy6ef7iEliYa4l2k4Z1RL9ywLBNfrKsGPWtBgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
NujYJTwjsyrlqUCdbB_RvObpz_ZX-F2-3f7VXdgB0iwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
TbzuqF2sCLdxYIpiIuex3DRyElYYG8KJZAkaDNaXYjIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
9f3ry53NNcNtc6NBvQzQlFPItSGwXozn9GAxS7ECEMkC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
drjrUDJlcw57y_nHQzCPz6lSJ_RGukuNScfyqs_iOewC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
D7gp59OpUnCrTtMWvJ-_DeqA6-1CP-SJpjximm5qC_gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
LtOKhpD1pFqUXhFYxFGL0NLaIcDkbtIPV023J97A3HoC
[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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
UJ4GZVglzEscP7UW7UFWgA6uETlaB0o_i0hoy5W6dH8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[cipd] Update luci-auth tool. To pick up https://chromium.googlesource.com/infra/luci/luci-go/+/df89453c17a R=aknobloch@google.com Change-Id: I18d274d6b5939c38aaa358a20496e23931ea5658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3880626 Reviewed-by: Aaron Knobloch <aknobloch@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
3 years ago
git_revision:f4d33857b83ff401f70d3f7b5545bffec9ff7b98
rONsv2oSCvBTXVHHT268YOBEdF10t40Urswq7jEz4W8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
HrAH5DQUoMFmEGUoagmCDaghSHtdK6m-NvsYlnllEGEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
NAZOpQK-OL3X7ZQ0EwHPQCcebYxdngtzBaIr1eQFfx4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
wRW6lmvPrmIQwwrMXlVySnSe1dQ8gV6quTbEJO_5ad4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
H3UYa1q2N2GKXi-Nr8vdOFbGPPInVwsQmpAkHbu3-6cC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
rqRPr5AgS4UzKWIswOdVoe_JASyfWm5--_pGP1xW2z4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
UIGDCOH_sM2yqJ3ozcqqxVZtMaastGSZ-NHcn60oyx4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
6l8K6uMfUIy994xjtf6KjsBb4bZSgtYUABg8xk31qpgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
O1JvFc5UTyFvYOA7eKk6h_M0NxlC10WFLGqDJghhQogC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
T86eUAfJKmT_bwlPb-KyVL_3uIZpRmWzDsZO16r0ALMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
JiNsCNpzfTIiHtCp-W-VPYQ9eIKX9lgF8Q4ROR68XH0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
RNmkYJyVXEmE0QbXacl4neATV_Ovfbbtyj3HRfiuazgC
[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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
zyWTi3rxt7MZcsBtkxzWtGfcc4lJj2l2YucuNP8vhK4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 release change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3814095 Change-Id: I3bd89d41517012d99db9b523eae1c63b5149cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3812233 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
3 years ago
git_revision:f09dbc988cae854052bc20d21a90089d9c188119
8st7Q0mnGdFluEUA2vShxMZDwYc-RaTCtkiK0-1ADpIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
zVjqLhwKbteRLwkrZbBS98mzymcbYvU4CAhUqRva03kC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
xJu3u_5W1g60imSncNwM6mtG-GtHhgOivTiY_ymuOqYC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
oEbV0TXrFakMu45aaFqBQUjPS3oTt7WCDyT-eZ7plwUC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
XP6bv2mdpB1UzV9HSMHYFP_tQt6wMyacbvu-pDjKw2UC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
FUq7DX7SGkbQiIE6fOmyj0iy1Yx5gWib6ZFLsi4i9o8C
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
7_S-1PLrGar6IMg_LM9Kr3cq2c2NnQH34pKiXq_xTuQC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
UwqiHn7MpTaWfC0p7XImObXdz38Vy1zlIhKYSZdTKjQC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
Ffq82vMu_JynJylAGlNJqrf_5zGSmtnRiD4sVLV6GAYC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
AGmlq9AFL3GW79NQwNeMiWKx925sgHfPkgKmbfvj7AwC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
I5E8NXkZSOhTLDbDdT9TcGFRPXH_O2Mwry5Sf2v0RsgC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
5XksAn7zUOvSAdRhIu6G8BOTCJtiS5-asOhw9x5w5VUC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
TJ_p6ZWtMBPSQaEuP1g85R2L-Yvk7saXWbj7FBsKMgsC
[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 from 1.33.1 to 1.33.2 Notable changes: https://crrev.com/c/3907690 starlark: Allow use of CV's NEW_PATCHSET_RUN mode. https://crrev.com/c/3933137 lucicfg: belatedly bumping version due CL above R=yiwzhang,vadimsh Bug: 1242951 Change-Id: I0613238925d6fd2c858195e47421f0856a0fba7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3936723 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
3 years ago
git_revision:5ba2f7f0dc8cb2b11f292ea3feb79015b25120d9
CK-vX6Ylw1MJN71t_NcKFraKbFW9FEo4D4pQT9tE030C
[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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
oWGrgk_ANcTVHjndYUOfroQ0Via73p9mRKjMJJwAgGUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
XQxtJPiwHevSlqESfrtvcTcnyr5RFdhZ6SObC-qjr8AC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
t1sAGa8hCJOJcv6e44SeKgGHLcgRZeXel7mhFapILQgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
FHXhLnb5LfKlHuSm7N7vzn178SUCnXAjlMc-gTnTNA4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
rtv3q-b6v3bGxSw_9fRAUCFgF2aQDMFmgo8zLdjZ1skC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
0N8_eK_phLZKyffC_ru_fvGhlfNOImcx1hHansGygYMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
b_DJybwJ7yVrBomaYzBQ0_P0uVJUe5VG4V10mRoCN7QC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
UOn_WPwePhYfsNM5QU4gGVDRjfbtlz0BcB6NZu_Y2nwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
MR6WkJx-4q79MT1zekQ14QdSxp8SUBSKwSA0y_KHWwAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
ddiKQzp4n0mzM3OpFGCVoP644xDpMVyvyYWcBbmlFBYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
sHTNOb-AAR9CPfuL5J314LNsJr0ZpCnQwwn1Cfxci_gC
[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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
_j19AOaSSjnz6gnknkrkQNyUA8nWHNwFmV_4mJC5gkcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Contains commits: 7979d954927af292bd5a57dd398a9791cc43099c Use the full paths of bundled interpreters. ededcc9ee88d285f6c1ea6154b0c61da5cc6fd6a Provide a way to pass in the full python executable path. 376c57dec286030d5321b4aeffbbc26dd297d28c Add a test that inheritable file handles are passed through to Python. Bug: 1318617 Change-Id: Ib163c6b8d88667dcec5afe975006586d13b2b2f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3787826 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
3 years ago
git_revision:7979d954927af292bd5a57dd398a9791cc43099c
yBWGUVYTDDCzwvrFWfB5W5GIRSKndvSK75M1m8l5qfUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 uploading Xcode in legacy format and not excluding some folders at upload. Bug: 1348212 Change-Id: I2a6b635a6c236bf2eedbbf7855da3c0d58b4abaa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3834034 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
3 years ago
git_revision:d14d3b7a182f083b41d2df282885d3db210eba79
d17Ijg1_sD07eNX6ZeqC_YECqAXie3v4j-g_HtK4JwAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 uploading Xcode in legacy format and not excluding some folders at upload. Bug: 1348212 Change-Id: I2a6b635a6c236bf2eedbbf7855da3c0d58b4abaa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3834034 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
3 years ago
git_revision:d14d3b7a182f083b41d2df282885d3db210eba79
zpxMyw-nUSR_KIrTn1XCK63frrhYgf0QNklzO-sZ5pMC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
POc40M6NUTlzhNhQIKC6DNm0XJmBil-7A8PiqjJnDGYC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
taDYc-RNOWpPQAdZ4TzFxrj0v1VVLDqXD_Kj41D1HyAC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
bKoR9uLEbuKWQ7JK_Z42eEIWjMqtlierza-R3QrccKMC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
DTrNxafjtohjGDFvLtVb9meSGitdFq3s4VwzijxH4HkC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
cdds7XsMJUFz8CMGu0bChK3bjzgv_c1DP7stkOfNzb4C
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
Nf7zkHzLrlx39GGoUxo6p4N49bFHmU2aSpB8kJlqG9YC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
a8MUAIPmN1w5pk_P0nxnjXHxJu0MDp7CsRZIfJuaL4wC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
ICnAGWhXVVcERIRGnApxyN_XkjndWAGfgflJjOYc8cgC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
2DHyYdKyZ22woFqJBHsGybxZAwRcgbsJoQpQSw1jSIIC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
8cd3p9vSjQbuWe2_Fy8LUoPC7-FiXuJDVNSjxdK3pfkC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
ZSdslvhpl29W0eax9w177q7NXNHslf3hWIY_70KtrZ0C
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
Ml5nEUUZRYdqvtV57KAx9TvTppkrQOhhduRLgLJd9soC
[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 Include crrev.com/c/3779863 via https://chromium.googlesource.com/infra/infra/+/0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` rdb rollout example: crrev.com/c/3627691 BUG=b:1337692 TEST=No test Change-Id: I8407e55ed6054131e091a494ff7c016a346f0b5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3789454 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Zhihui Xie <zhihuixie@google.com> Auto-Submit: Zhihui Xie <zhihuixie@google.com>
3 years ago
git_revision:0fbf0c3c84a67bca202dd5002fb38bd93b08d0a1
2rVhnWGm0qwdXeZLoXy12hf-mG0aOOV3iTXgSI8vGTAC