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

515 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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
9vU038s1CdB6obFrS7ASzJPgo3unwlbC1RE93pujm4kC
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
fj_n4JALx9z6cvqCwVa36SReO92qkNNTUBWaKT9oBg8C
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
AfcR5khjJfmqJ0xpHaBWLFZDAeRh1LQ1jWb7vWjoe1oC
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
ZiPgLvZ_JCJMm0lxY_1ebCHJD2rRFO37DxD5SQSuIxMC
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
8EUgRBVg44htOWzLPo7Ma6KKjFtqcipRpJrHSnX2q_AC
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
HMK5HrindDLJ2PGbR84u9iDSjzqVWL9C1wI4Eq9cAFIC
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
ECON7Pn11S1L4irIi9dxDBtcSbbSJd7LuqN1yh9r_74C
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
tspUEz9rUWUD32-jX0a45sFzlFFBkhTdwYdgmydv4Q8C
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
fYNqy1Td9laRUJj9Ar1NAz82-bmhIrJtqNUY7qoHhXoC
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
iC4nUBFzS7lx6w7RMYrenxNsuL9YVhUETC2kDVU_VAoC
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
K8LNcss5d7JD03_n3L8YMAuQQglNmKWc7AZEnKlqMFYC
[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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
NKCXFOnrq7EgAmyKvoOdSc-3KNEKqRacrYy_NkCqQoQC
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
[Chrome Health] Update batch priority in pinpoint CLI Bug:chromium:1363444 Change-Id: Iccd21f1043d6494b192bd977c048bc4546865fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3955705 Commit-Queue: Leina Sun <sunxiaodi@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:06230fdc34c20ba24a242db1daba3426704f61fc
v0td-Bxv4Ik8Oe-p0fQrFxBzg4UcnWWwU_EZdb82_rEC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
5 years ago
infra/goma/client/linux-amd64
Roll out goma client VERSION=255 Bug: b/256548869, crbug.com/1386100 Change-Id: If9367944461e8b4d1b775a087abd8fcc1a224b17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4045102 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
2 years ago
git_revision:9d557608987ecd97d7f63befe1ef597fa3dd097b
9NoTFsY-wYeSuPFt7DfyzHHeUvXUs1sGybxe5iwciTQC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
5 years ago
infra/goma/client/mac-amd64
Roll out goma client VERSION=255 Bug: b/256548869, crbug.com/1386100 Change-Id: If9367944461e8b4d1b775a087abd8fcc1a224b17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4045102 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
2 years ago
git_revision:9d557608987ecd97d7f63befe1ef597fa3dd097b
Mcdq7UitZRCPFNiJf6Fi1HA7FKppQ9DH-ZuB77PZCuUC
Roll out new goma client binary VERSION=216 Add mac-arm64 platform to provide goma client on fully supported platforms Bug: b/182514677, b/183118231 Change-Id: Iae7581883d403a1a28f7d0bb1b871c9cfd0f7e65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2816481 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@google.com> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
infra/goma/client/mac-arm64
Roll out goma client VERSION=255 Bug: b/256548869, crbug.com/1386100 Change-Id: If9367944461e8b4d1b775a087abd8fcc1a224b17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4045102 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
2 years ago
git_revision:9d557608987ecd97d7f63befe1ef597fa3dd097b
boaD9U0wJHmg1Gxinw7tjkoNPhpYQWQIrJP5F4GXefwC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
5 years ago
infra/goma/client/windows-amd64
Roll out goma client VERSION=255 Bug: b/256548869, crbug.com/1386100 Change-Id: If9367944461e8b4d1b775a087abd8fcc1a224b17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4045102 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@google.com> Reviewed-by: Junji Watanabe <jwata@google.com>
2 years ago
git_revision:9d557608987ecd97d7f63befe1ef597fa3dd097b
_MFMczZWKzsjxhi3dIY0bve0tUwuQ_emRyw8go1N4dYC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
5 years ago
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
qV2OwLxPrZCfvgSWRxaZoM3-BosQzxglF2yHWzMoDdsC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
8_cSH_bEVH8fu2Bwqs2I_naZPiIAsn6muwvGuC8xZLYC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
Ph4PMf7eFXvrFO4-V0HuCwCFHFLdB5EtLn_I-miwZnEC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
D5lYlLh95nfqr0D-L0betVy3bZFM_jjegIAoywZkKjUC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
vtVgBVZD85exAK0cSnH8kXREZ9GUZkl7Wg0LElDPwNgC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
cfzIRx_tmFiHAJRXBgeeO0t5plm-lq67iskf2-VDIVkC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
niLQdRKeUDUT3CrAiWTtgPH00yU1g945ZfbC0nGT2l4C
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
IGwIP937ncylxJGjJcuRxVkScziGbike2FXOkWlcL08C
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
LTpd4o8wLaqw-ruyW3y6R4ERlKLWtGjKEIhy4-otp-IC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
NruZwREv3Xh-F5Qxw9IEZ9CDhHAJpSNfisErmdbriSsC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
pX8l6-DfLlOAM1X_461mz7yH2GyFAw5klyE_jAYHQ6cC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
6D4P9TSS7741Wzk33WUUTWdaZ7pgOzVgddKKFD_mf2UC
[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 Roll bb tool to the same version in https://chrome-internal.googlesource.com/infradata/config/+/c781c121d88b4f70e7e26c612edbeb1623a9235f/configs/cr-buildbucket/settings.cfg#96, which has already been verified in Prod Change-Id: Id30486841d65b598012210de7f6a1d1ea552d919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4094461 Commit-Queue: Yuanjun Huang <yuanjunh@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:f13670aa4637a5dc9fd70e89e1a378873d912f0f
0vsTWyAyk_5Co8eW7DdhAXeorzWmuPV_OOId7MLviKYC
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
HDYIew9HU8nJHf9G-jXEwUFPmraT0KqgUfgeK2LFuF0C
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
NHQ6uMJWoh87I_sYeWEizeaOvp4mJ6yuNzStpsX_owIC
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
PmhGFnVTW03DnWib8ygzlr36ktHVIVKYUacr_0ESDdMC
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
QgEnoJIel_Au687Y2e0M4SviOPK3KAp-79CVoE-ivc0C
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
ILHwYykaDQkrgQmfU2_1WyXBsHZjQByjSyDSdqzgrH4C
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
P1vHrXwsc0qDIRIskZs_KGUFytKOcUDnPqLrsfu28kEC
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
uaRgw66iQfzNt_tCGZ9Q7mgmrPR-Wyw8eDZCiumW8wYC
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
TOvhTmZG-_k6RoJKPGbHpMSO9kjS4-8Vm8ZIQw7onzwC
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
gEoX8sWPKpDDBws-85WZhEIzBN-SqAto8yt9qAvlf6MC
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
hRyYllysf_zzAQxg_dlkTHWgasasfNQiLbs49aRSKOYC
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
MZB9O-hb8zzt34rizN8PMIe2VetqhI3YW-_FtuIxDdsC
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
2lXMYG9FX36tRQqKks13YPNQW8pZgyRYqh90VwejSy4C
[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/+/4144455 Bug: 1402202 Change-Id: I798dfa8866ccdb82e0c9c684a3c5e4414c8f8962 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4146187 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
2 years ago
git_revision:c51722d421a69fea8888d8133cc7e9b2b7cf937c
tuA7dtmobL2_Y2i7z37pX-Ai3DQcv5DNOIY7Mp8jXKgC
[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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
S7S7yxZ62EO9-MxoguEnJ8kC8LauqKG_zxbDnVVQ3_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/linux-amd64
[cipd] Update luci-auth. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
HSjMYcMrGa8U5nZ8v466K3fXrY-5pTrVwGRQr-TwOpMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
95w-aeuC7iHTXoVzYCtN000UAmJCTvSe3MyxqyyidtoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
UhxXeFay7Al3rJU4qbjQEivUPjMYjSSrQ1Qp7j99Vz4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
FQGmG39yieXGJ5FyKRL6ieBxNr5l1rYeingFvQuN1RcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
YIL23GRpDixcQA2irSvPkOzH6w3JNc7RrowFVkHyzBIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
e7UfOZ5c0-UDCUuWImedy6RE7HMV0ZUR_AoMHhMUBbwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
BPW_DkduekZaPFrMEUViDK1viUz1EWX7yNxSH1xve3AC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
VXBWn2gWRPkf1I4XQ9JQjsDqcMIl2ozk52MgmqDPnVIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
0xbLtQQ0nQ1ZmObZeQAUHYgC6ezCsymBnYoadIsOcagC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
fDBxZCUSwY_vv9N8QQ5blscucIcOysx5encILbBz77sC
[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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
BGSsnu7fNLBDm5HK1aYFncGMr1BUNOkuWUY_eB7loAAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. R=iannucci@chromium.org Change-Id: I871fc01f25d6237fe982ac21d9a5d93b092ef4c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4004609 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:f2c63ff66a72318545da61612cd5e6b4872a31b2
ziAzNARkOWbviBkMopRlxowcJieyA_dv6ShCiR5wSjoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-386
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
m9_49ckxljzt8x3ebzxqeKsRJ_zunt4Lt5m5YsNsOnQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-amd64
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
jc-f_eWwIS3nEvX_0TqfEickV0D8txhgptqaM5R2l2gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-arm64
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
i24LhREzNMz1yFhijuHPLUoH6dc-luxeHFsEFayDH3AC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-armv6l
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
y7uq0tUtfrJ9OARyJZXZNStw72BnBXNEoCGGd53b-FsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mips64
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
yB11UgZEoPYhddALvx7hA696iWqxfIofUfP5YDaJhu4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mips64le
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
UJMXS1hShg1F6EuwqsEXm1hpgZo-20fJRDqh4Ud3pXcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mipsle
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
jEygB1JFm5KHpbP618fa8y_g-6uMa5VTGvulRP25YX8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-ppc64
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
CWkcaJs_09AGyCZXMFGIoa-25759tyXD9HBUY8CRteQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-ppc64le
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
qYaqWtQGkZCsMgxVLPB1oAzGQ9MM-xbRZx6QhAT_VU8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-s390x
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
WQSEP0Z51OvtkFpSTWmJ5sUyMv1MaHHD0Fb1HbQs-LYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/mac-amd64
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
bYYgP4H29FGN-mz-sPlSrkHVyaLuUhHFIwRID8EMrlwC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/led/mac-arm64
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
T35QQsjMbt0zeMcAEi3HGYLJU0fKB4q6NDtuWzHTcKMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/windows-amd64
[depot_tools] roll led To release https://chromium.googlesource.com/infra/luci/luci-go.git/+/42f95c25b24f03e440ca1e19ae1e8e4c0c44d795 Change-Id: I0af5281e8c88da9b3fccf86cb11bf39e3582d5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4086338 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
2 years ago
git_revision:b577c5441156c22f7644bd961fb7fddf3d44bd8b
eT3iTORzTMc6oNAWvWAGfBHZeSBYrOhN9W38CQwG-pAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-386
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
5G80r2cOXJxforD2c-qnA4K6JrUtI88PJSvYwj0SOrAC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-amd64
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
zOsg-2dPM8w9zxPb5djKxjTsQYvBYNHFirkBZb9V4QEC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-arm64
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
KlBNVOOaKyPzdQZJFi5CZCUyO7e54k7wv66cgAv2JrcC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-armv6l
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
QalvW3I7-yIIqVeP8_YK6OovWwotCOjMqIXUyVHbSucC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-mips64
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
5RTRbifnLND3EXycCllJgJnzVjLsDPlJydX4NK69XRoC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-mips64le
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
uxx_jVOGZv9kWr-IrB9nIuxw7SdNFyoQFZvBLCp619cC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-mipsle
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
HZcwXRwm6nV-HD0y52M7sjlK2gqTCewACEXLuu0pgSAC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-ppc64
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
PT3GwGVhdYNFuj0d7oOdb6hd2YinS3CQnctC5YjpxM4C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-ppc64le
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
NGX6k19UW2cCfnXRH5C5rgycM36ND9-oBk0T3qy90RAC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/linux-s390x
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
CbzgRMK3wXS6TDV_FSQoQ6KxoDYcd_JcPrpAhPJxJZcC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/mac-amd64
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
OOn3gYzu1t99kAOu0Tvs1qVlwAzwDn41mD6amhnegHMC
[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
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
niUe1mdbFGoSqpS0WMK5ZTyL-ih8CTg_9a42TnN1LkYC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/luci/lucicfg/windows-amd64
Release lucicfg 1.37.0 stop generating unused properties triggered_by and location_regexp triggered_by in CQ configs has now not been used by any projects for a month. This is a deprecated property that we don't support anymore in CV. location_regexp and location_regexp_exclude has been replaced by location_filters and is not used in any projects any more. Related buildbucket config change at https://chrome-internal-review.googlesource.com/c/infradata/config/+/5229868 Bug: 1395209 Change-Id: I4e53606c8bcd7a784970beb337984a808321c5a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4113683 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
2 years ago
git_revision:7e6a72cbb3685370208ee0195bca68f3a3fcac43
3YK2s5sNt8fgPqzJRTKpRNdAlBbKUDvkMHtUro7uz4QC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
-DqrW1YY1T_BnoblxXK5gsXsxLIlI3UiNijgKDCHVXIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
Gz9krHL6kKjbvGdxI5atUyCuwSXBMIhmVrK6FblTzSIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
j94ptZ4Jhqb7Kucuc5sUtMvNTihGNp07xqwmtYeyAKcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
YHClLkt2SXTET3UPWDUEerzAbPL49QCzBzPmCXPrYFoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
VOe-uQoFiAg-7ZZRFRXt4EKwTGiveObQ-LrO-iJiIr0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
9m723rVpHjKQFaFZoO07pdPS4ihDkFMMwJOmEmmBGWcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
-64acFnU24T7vjNLAZhudYzf_S_8TTPZs5M4aOVrcW4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
exYhv24o623wpCvYMC712pZeIrLqGbbj7N2KnKh2mVsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
yLpdb8_BtEP0ou_OILEQQFhCrsm3BCK_f29NwFBR5n0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
Iy7mX6ddOS6xw7RJL_ZaC7wZW5PvJBamVVIelOeA5OcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
HNfbeV0kNVgfOttEgK-fq538CSP9Q5e0aXCoewaiw08C
[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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
8g1b8S-MpuAv-K5pBtjvNCzaPZbH1KBeMIgJfYx-PjkC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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. Changes in this release: 55ee5cd215996e99b807bd19060f8c6845423985 Switch to a buffered channel. c18f898c8628f7063328a553de31b5a13ebbd47a Fix comment typos. c55184b5835c789d073ce8ba10745cc7efedcd65 Fix typo 50e0d6a61bf2706e8096a4c3785331f2fa1f2bad Fix some warnings that are causing presubmit errors for the 2.7 fork. 39ca9cb80c0c7f5a18bcdcc6ce65bfdb1cc64879 Update vpython deployment doc c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78 Roll chromiumos/config manually to fix the broken roller 149a1934123a29ca32c85f73597e7ffbfa7dbf4a Add initial PRESUBMIT support for linting python3 Change-Id: I1155342ace04e2944a9abe531e0f8b5d0206a0eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3951269 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Auto-Submit: Brian Ryner <bryner@google.com>
2 years ago
git_revision:788e09418ced22000a9774e4549b9ad42084b814
9xwbxh5Xhwkp_6m5F96fosvt7HuBtDp9oqHJU4urhxYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/mac_toolchain/mac-amd64
[mac_toolchain] Roll mac_toolchain in depot_tools to latest version Including the following change: 3949129: Fix mac_toolchain ios package content | https://chromium-review.googlesource.com/c/infra/infra/+/3949129 Bug: 1373792 Change-Id: I9a0a037d495f8d1eb4ba838b7312e5f6aedac02c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3949012 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
2 years ago
git_revision:febf962fa9e6f5cc5c4ce86e8dab6ff6d91088dc
QT5Z7SqtISM6t43Aq2EfIZhPsoltf4I3TL5_VjrhGmIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/mac_toolchain/mac-arm64
[mac_toolchain] Roll mac_toolchain in depot_tools to latest version Including the following change: 3949129: Fix mac_toolchain ios package content | https://chromium-review.googlesource.com/c/infra/infra/+/3949129 Bug: 1373792 Change-Id: I9a0a037d495f8d1eb4ba838b7312e5f6aedac02c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3949012 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
2 years ago
git_revision:febf962fa9e6f5cc5c4ce86e8dab6ff6d91088dc
wN2a62YXBByoREz7owfdlpk47efG7dq43ApwhSYY9IkC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-386
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
0jh5WJiKY3YuD_Jb8PqwvoEpkIErWxDjPK1zHJt7AWsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-amd64
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
ifuMgrBw52FZoNeCoOOBKJnEOVZissbo16oyfdNNFR4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-arm64
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
37GBPQH01OFQ_mNexmZL4JXvTJrJZ6lupI2oipo7NygC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-armv6l
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
p5RXqsNOyauZgCE7fUiaJjjvfiyOaduXWxsPi79jSusC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
5vO0g5QLGwZINTFQjnhKEEMDTaQ2geUUP16w3T7icicC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64le
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
FV4lcmPr2Y3qx5dC85IxvN6j26tgBTIZY3KL3OO6ggQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mipsle
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
ZLw57efe_OTsHW_Sl5W2tK29zOx2xEi7m6XqQVEAS6EC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
1KLg18xHw43xbVYfPMPXBhqANzzRwP3aYRl0wi3qohIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64le
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
hKB-qdoedy6YFlpMY_B2sNmhdoJzQbcRRU-ivr_nPZsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-s390x
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
Z8errTmVek00stSE8njJ4agFHThZWdziTgN5qpNDFbcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/mac-amd64
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
SyQL0RzHkWotXKicxXx49tVIBYW56N-NeDSB046eXwkC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/prpc/mac-arm64
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
M2wFOESsz-1S_BtbL2dKzUhxAspQa1OolA-J954ggjQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/windows-amd64
[cipd] Update prpc tool. To pick up `-use-id-token` and `-audience` flags. BUG=1204034 R=iannucci@chromium.org, tandrii@chromium.org CC=sdefresne@chromium.org Change-Id: I1a70115d9833d10224516edd6042fb9c022fd38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2904101 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:5a038afb97f6b77e0fcefe1185317da216fced1f
pZ4PpzsgPaEjhtfUbbynrRQQ6e7zNBnEWnKn6aupqyQC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-386
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
5Wvz-jm9CRty4Xu9P6Zaxikp7JOgGkPU62oAyHFzg5IC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-amd64
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
2nQRu8urImzYe2vp27NQ_2Zb_Vu8fCf4g_iI2l3-a0sC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-arm64
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
4BMRjeCRsObAE1Zss_hD8du2HGZP9rAipoSwCjlm3bQC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-armv6l
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
sfZ0PzPR7uG1UOs8zbD4yoISDqSG0lWt-nmtXq8LnjwC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-mips64
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
iy08s0WCWEQa7ufT9uiECKWC02yxjWVj7qZwl4bMgG4C
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-mips64le
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
pk7AtwtCc11Fbo43WOJ0pGek3bmycs7Ia32e9mVc9A4C
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-mipsle
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
iwKIJdhZlEbc8Nn7TNIqywPnDL171u7OPBo6skAOvdgC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-ppc64
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
_NERYE7boju4P4vliZet0OZ4t_4io3HxElyqiszJPGgC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-ppc64le
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
-97u-wOUEulIhOyP_JDFZybqZ3oyghmOuxrvTxUcVTAC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-s390x
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
x8LKxMtiUgabkK-swSVPFvWYzkl2Y-O0g-jYnLaBE3cC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/mac-amd64
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
0_ZvqOIZFi5AIlvuWHrHElT2DnXBsRazrZHjMKbIh5AC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/rdb/mac-arm64
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
Kjt6FRp3BzGM5n2LZa9bK0HXcN3yxcL4ehQFmxv-3NcC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/windows-amd64
[depot_tools] roll rdb To pick up https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4127735 R=gavinmak@google.com, meiring@google.com Bug: 1373762 Change-Id: I811d3dfbb6a158996394ad9ec13674a90a9253da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4135663 Reviewed-by: Gavin Mak <gavinmak@google.com> Auto-Submit: Weiwei Lin <weiweilin@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
2 years ago
git_revision:50399befbe02a980369b270c878fb5a4f0d38824
r8BCk4V471qySjs-msNPOnSyNF17WIdgZDHFLX0OLw0C