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

559 lines
18 KiB
Plaintext
Raw Normal View History Unescape Escape

[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
# This file is auto-generated by 'cipd ensure-file-resolve'.
# Do not modify manually. All changes will be overwritten.
Add crosjobs to cipd_manifest BUG=chromium:973247 Change-Id: I8be6386fc3ab9ce6e8d9558862dfd0a7c74a5e6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1743018 Commit-Queue: Yaakov Shaul <yshaul@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
6 years ago
chromiumos/infra/crosjobs/linux-amd64
git_revision:ed616d595eb7241d39d34907050d2949121d6ae8
_vAeU0Q9lAxn933K8vDhwGK40zKVvV-yXGpIy43ATXAC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-386
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
O6ChffXAafn2KNzLFlddCOEI-UPJ3Jg8BjNhoCcQRYUC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-amd64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
Ufsh7Be35nTha4HSYeWCX3aUdzDMUmj73-OwD41lscEC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
5sj1Sz66UVmm-Q8wQH85flz6iuVP4kqsRrp_lMxLEhAC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-armv6l
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
S_VnGrTQIcCy5sRDLmURowwAzVJbPLTAtlJJzt4WSlMC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-mips64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
ztUE3gRvvhdBRP8XPcumLBctolAds5dSLNTmrEND9KUC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-mips64le
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
FVFoczG2ycsHVtWIyTf421eucm_Hxv77PGvyotracKwC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-mipsle
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
67A4bL-A-wCJ5zqxHheBPbi79TGRORMT5YIjpHVRfz4C
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-ppc64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
m5mIhauex3Alscr4wLmF4ouGlr7wi2X0QHcT3kCFzbgC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-ppc64le
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
yzy_QfYoWJIXxnrgRKQxM0o54OrkfhCy63kVU5bC_isC
infra/chromeperf/pinpoint/linux-riscv64
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
re_gd_snZkAiqFjZ8L02IsN0P2EjqeqZ5gnXXgxLT4kC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-s390x
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
1H-JYzH7DPNpCdr1zNKwtt0N6QnF2RadShCAKENp728C
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/mac-amd64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
SlPCkUcb3EIvgazMeZNGVgq84Qn8wodE1YEBbvgq08QC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/chromeperf/pinpoint/mac-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
l4AehfpPb5LR_kqui-WCQX6sySymCuIdOLFFUTr1R7cC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/windows-amd64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
7lZuWtQZUHpdpKp_JPVx0F8vnkyAJiiFg7talumnf3IC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/chromeperf/pinpoint/windows-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
pJxQ0Hl-ATP8eyFijAa3xaYIms_8nfXxSX07XVxyKIwC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
Reinstate reclient Adding back reclient to depot tools. This will allow it to be used for chromeos-chrome builds, and other packages in the future as well Bug: b/270080866, b/242680623 Change-Id: Ibb800a7c36f61312d540ee5595c585493e5e3578 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4273546 Commit-Queue: Eric Lok <lokeric@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
2 years ago
infra/rbe/client/linux-amd64
Update version of reclient to 0.124.1 Fixes the issue where failure to read an input file fails the entire remote action. http://shortn/_7Lc4quSjb5 BUG=b:302230815 TEST=Build chromeos-chrome locally Change-Id: I8ff8efc789b0f22e967df8d30b4ebbed415c4cde Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5101699 Auto-Submit: Eric Lok <lokeric@google.com> Reviewed-by: Fumitoshi Ukai <ukai@google.com> Commit-Queue: Eric Lok <lokeric@google.com>
1 year ago
re_client_version:0.124.1.13f78cc-gomaip
LCOZhNACP54nV-xYsKIGGOzlFnVyacNwmv4YzqxxgOYC
Reinstate reclient Adding back reclient to depot tools. This will allow it to be used for chromeos-chrome builds, and other packages in the future as well Bug: b/270080866, b/242680623 Change-Id: Ibb800a7c36f61312d540ee5595c585493e5e3578 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4273546 Commit-Queue: Eric Lok <lokeric@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
2 years ago
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-386
[depot_tools] Roll bb Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
N9nQuqLy8iLZY-qU5Odg1QLMKA7fBZw14ChzP6BbC9UC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
HH8MAsY2V5cHWka4DjGvYPeCuYABVfy0jmQyLgmuyvUC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
eZg0j2IlVBW9YhuB87N_53DdGILiFtxT8XEkdx_VCTMC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
dpHAB6myTRlcJYpw-2EzcUXaCQyJeDOIMHiwEPUEV1cC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
QH58VVNy6fcrF_6w400Sg_nryBLAbVbNv6F_DAE6xMwC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
7HPApWY4HoXZ7XiSrgmWT2-2IOJTjaBH-ULG-HOPjEkC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
OE5RHmGQbuLW1QFl_2SMebSS2xut5uZ4wtWnPoVilwQC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
Rt5scP_9R7A5FNNi39hXhxkJmE0ue05rYzuVut-6GyAC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
UKpUT12II0gMWoU43bKgxnMiJyKadKNEwRIIOxpxZ_YC
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
infra/tools/bb/linux-riscv64
[depot_tools] Roll bb Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
1qa6q87EokDSFQJNeIb5Po4oACi3S7h24YVz5zke39IC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
7fruWKiDZ5sRoYql5lIDTfvEPbb629g1zdrOeGjBdHkC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
YdUerVH4Uz_NMErYFMy9ct2-lGSuffe1_JWvtSthy4oC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
ebKsNVnssT9n0URewx4DiBik-vycVaecIW6L4Lj4HCIC
[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 Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
WrozlgioeqqmhtjJjB3OiOoYFb-L-zcxzm-dMv0WargC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/bb/windows-arm64
[depot_tools] Roll bb Bug: b/325130915 Change-Id: Ie508259f58aae213c4809d99b3077fef949f08b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5315098 Reviewed-by: Randy Maldonado <randymaldonado@google.com> Commit-Queue: Chan Li <chanli@chromium.org>
1 year ago
git_revision:b1ef34e3c86269b1261ccbc039ff2cfe3baaa961
OlF3pZB7sxFSV_m6_SETa6lI7KhzCiL3ut3JV0Q6wF8C
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
u08j-6ZdnY1jYLeRsfU_9AJ1TDApSykOfdQjDZphylUC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
-TSbLePCLnpfZ22Psg-vmZrh7mx5S7RCujkx6R_ev-QC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
u6_AXINx1AL_jc8gYUSMEdpIMj2C2M6FaUeF6O31Z2gC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
3TLxxdCJBoPHWYi1IQiBUUeKcjRbBa-kU4o0FnUDzhoC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
0fkBBru7CB6p1-XHliXwJuK98CguIQPuNRrmPZHhPjEC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
lV4kVLI30z_4u1lt24lheTAtfWjyCxKJQ3idaqTHSIAC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
ZisX-rxLqSW2oWiit7i9sSMXY4g3qMW8wmrUErANDsQC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
Im_qwKK3C9xndTycfNOuBAWma7dfr_OS-E0KfeVmvlUC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
_yGwTPgTwe4s9A9-bKWDSVKqq1xcxDmlGf3qEwY6tnIC
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
infra/tools/dirmd/linux-riscv64
[depot-tools] roll dirmd Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
nt9rhHAcKsu3nN52NWZx1SSRH8X_NRa27UYHcUh_l-gC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
ZeauswrR0W456TqegV7qz7B7B-ZUJSO5whnLRFDnyrIC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
4y8cA_5h-XRBDQmD1spCdwj9Fnd34y0yeABnvOLBVNMC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
tlw_fdY8MmzLE-avT8CZx3VqZqTi2wAwAzbKpwgXlEAC
[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 Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
f0LWxnahbRqTjeaPLztCJLbAnpOyTIF0bHDE2RymsHoC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/dirmd/windows-arm64
[depot-tools] roll dirmd Bug: b:323922972 Change-Id: Ie6aaa987ba56b959c6acd31786f6c3a261679e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5296200 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
1 year ago
git_revision:9558e2c2dc002209753b8e61b83c4a2c81361fbc
Cfl9B4JQG13noONuyS3NIS-6qzO0T8H8KHGp1xvJqbIC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-386
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
uNNHQMTomXNDDRpYjZNMQMzf3gdtIDFudXjjsZvLf_cC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
XX3E-CiAQuA_JQSK4VndA3CHNX9-ahKQSLyI1v2cHQQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
YfPKuXBK4cjLjfaJ2NP2MQ2rYF7vVOrFsYejlVRznGMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
ls-MxnVeyUCGbNoW8AnrS311-iJuta66Vj4Ja4kV_M0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
U3VnLLariIs4YtiF4xOro4pP5epIU9Qjp-hgrb0xkpEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
BtGMG3V64ISYXOMyu6eBMwbf8w-4iU_AdqbFS1_pWccC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
M62m2Cidffem3aZdU2Xw0u35Hdtt7YICuGokTmSVRv4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
sCED42jWkRy1B-mxlJoLtZfc0btSaqwhfn90ld4Zoc4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
LNyBsbIiiIgGpA8I9ChMZJaP8Al1hha1_9w9JWn48sAC
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
infra/tools/luci-auth/linux-riscv64
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
Ne2uHHxRfDwtZfVszN3Dr3eMCC62-IvdK1r142DGZnUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
w2j19L7_F0GatUC6ChLgpY-dkRHrTD5ypooHQcVin2gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
asvSL3JSt8eB3Ptw9rUmaukqUn3e__2QMSp54GhWtS0C
[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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
_XHpDJIJzHLc5nzPE761Hfq7lR9zlofzwEFIHBSyiR0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
t-uVPdCUMyXUF6MkYBNjwp1M2WaVTkGavaGbryoMJfEC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/luci-auth/windows-arm64
[luci-auth] Release 1.4.0. This is to include -json-format flag added in https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5369304 R=vadimsh Bug: 328289019 Change-Id: Ib044eef9b66ea78c8a1ee902c15b47863264f435 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5379835 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
12 months ago
git_revision:02ffe6e2b222aa1f56776b8e5385f49687451bb2
LctndLGHwJNf5ISBA-IIzZClyN2SOd-bDH8eo2KLDCwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
ge-5N3T2kBzlysOhp2Y3b7DTRiU0N4GqI_Q3ELf_MUYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
9MscsPmNzDEXsue8XFb0B8fENKbCp9tkjo4EGsSV0IEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
0-RFNp_WHPOC9lkbGt4mYstxy5_MuNxGJRSID98EjDAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
vZ-PZ5C4c1f8Z6RIFLdq-qMEhIck9XEQqEmPyC0SIAgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
brIH1dblCsL3X-YAHdt1mzxmAclzvNTBPUrf9zXYz-AC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mips64le
[depot_tools] roll led Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
JyNFkgQCgWoJPYjDSXKrumSqAg9eFvrnYr0PVOAhuREC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
UkLrWhfhFun8ugbJWNU_IAimasncW5muClYG5EdOd0UC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
VGELa70k5iO0MeKYpg5fHO8XT--xMDtvUZ8C1XtbkhEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
7pPI5o97VmUkH4plX5YjFszfWiTWVyPNvJq5Ic_MOUUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
infra/tools/luci/led/linux-riscv64
[depot_tools] roll led Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
49xm_o4cHatC-rl3cX5k9IQZZLfxudiWQRvx4ZW0NdQC
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-s390x
[depot_tools] roll led Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
bmPgBQHxPS6hZGNLrR3yp_E7NC_7RXCw4B9dHETEZbUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
WX-4oczt8X0vGpwPbIH0r9PSQ9-MkCKfouc0lFWpSbQC
[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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
DqnH4qWTB-8wp6Zd3pg54v0Vk8NKvOcBLze5VJL8zmEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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 Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
GVaXQIhXWs3Ia5wTDRmkfMfeNGmTlbWupmFWBjS93wwC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/luci/led/windows-arm64
[depot_tools] roll led Change-Id: Ib9b9c046270c6c81841b9ac49c4f2add47097f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5490921 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
10 months ago
git_revision:037d7079cf3faced3842e597c9dfcc7475b2ddca
86USJHcBusCFGXpz1aDjQD9necbrmXKnCtNCvMO3PjkC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
aPnjoZnn_jr-hQiPD14QiDRrvhqIppxbtwbkHecaTL4C
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
N2BS5b0luVZBRfSWcutKv9OaR0LHL9n1inwCD-1AKZUC
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
dmwAcZgcq0sKOAQcDubAYVnqmJTvFOKLt1_ONjcriSIC
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
HMb38t8jOpP7kuSQhqDng7CF0ndoZI1PTIgodzhRznQC
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
otNUpA_vkM87uLeQpK8b2l0-bJ1B99-y79o6V53BCT8C
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
bgKVqk8rfuGhKdA3_qhE5Rq8f8mVTzFWkszzAHddFdYC
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
qqI91B7pNRR5Ro7EXzDgr2cEZ_UGsVLnivN_pW9D8PYC
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
s4iHh4_m2vvbXDfDSM7fnE-koUsU3MvyFijsnNsVwocC
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
FiIlD1TN1wLlj5NNpPIBYi7Ra78mjw4iV7L5dx_hCycC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
infra/tools/luci/lucicfg/linux-riscv64
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
wMp11ObHZ0j2Eu96mRQi2p4sB15TDXEP6PoY0riCNysC
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
[cipd] 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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
HVE46G-Eo3Jm7J88OJAUpnJNmdB4p1miMqdGHodBR9EC
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
K60nKBbNe5odOlHgUC2ElEKyw2dHaiCAcuWyuSZA8SQC
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
t_pFXvgM2R-eC0MLxNCr-u2DLbc8YfDYgUoR2Cg63ooC
[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
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
lcmjTVLc5z-72QCcJQUPqY-m_bmYDmaGV2xxWPEpN30C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/luci/lucicfg/windows-arm64
roll lucicfg to v1.43.6 Noticible change: https://crrev.com/c/5449899 Bug: 40287772 Change-Id: I9f8201e72bf0492f721c1d95792c333279896527 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5459860 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
11 months ago
git_revision:41fde39fb8468c9b857dd66d9d63c3ad7aae2967
6_6mrDFKpfLBjqtWNMSMdE0oUCySyamPn3Zd7pL_nXkC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-386
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
6stxqf4p-lttMDNhxIG-IWTrdIHddjMBo1f18UA5M2sC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-amd64
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
Tr0RRp9yTUHKXD56Zri1YX-7VQAFjYQhA2g5kILeE9wC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-arm64
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
02uyoJJvsv3blq97ynRCcWJw75It_rbPshUG_8fU0CMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-armv6l
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
KC2G5b2x7EPhMyPmimH-iBHo74etGGeo_YVuzM094uAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-mips64
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
LoHfHiQR1rmaWmJklw-e02nLeEyMSwI2kfCtHNrKi2gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-mips64le
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
vKlyxsTKBDxBMcrHmD00z7IwL2DnoMKcNpS4hHvvHFUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-mipsle
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
3EBoi-OwUsMMJFibIejyea4hJBLpQYP9rUQPCor8eEgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-ppc64
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
xB6h1G6Ra3nUQy_r_Kz2npvZ0rtXosIOOWgt3Y4Q37sC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-ppc64le
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
i6fXIoi5x5I7C0yNCqwmkleHkXUXO27wfAUPZKID6iQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-riscv64
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
knOVQNWNorfBsf6arIV_6nDiFSkE0ShyWUrK4dgKAAAC
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/linux-s390x
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
Q0Cp0RrnNtgKaxaeq4XKs9qiPu1botnPjuw_0EWxduUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/mac-amd64
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
6zVGYOzWUavhnRAhf8CLxS_YJCpOJD84lkaqt7tmrtsC
[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
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/mac-arm64
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
eReoZqsjPlArLv3IOto0daLwBV5tBuYZhNLgUxtQuQYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/windows-amd64
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
FxsoVTQhSBGLEBOFEGh6fFKS1gGJ-kFt4dGpTvbcaF4C
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
Delete vpython, leaving only vpython3. Reland of https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 Bug: 1376538 Change-Id: I6947cf2a54ec2b45b2540ad0784fafe73f44c441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5343135 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Eli Ribble <eliribble@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
1 year ago
infra/tools/luci/vpython3/windows-arm64
New cpython3 and vpython3 packages to depot_tools. cpython3 notably has a fix for bug 40148998 vpython3 changes: 85f17b39dc4cd404444e3567371fc2c2ee80b733 cipkg: url action should return error for 4xx, 5xx http response 074c3f38e2059adab777b0fcf38b6861114b0306 vpython: Recognize linux_riscv64 in PlatformForPEP425Tag. Bug: 40148998 Change-Id: Ie2e136e814cb62d8c5e8e2a380dfc0701a8f761f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5435876 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Brian Ryner <bryner@google.com>
11 months ago
git_revision:54edd25b784c750239eaaf07a21ed1e548dec39e
g4qGHJ1JWThgkBKT0_z8oBbp09vnj3JiaMValjYdSo8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/mac_toolchain/mac-amd64
[mac_toolchain] Roll mac_toolchain in depot_tools to latest version Added more functionality to support Xcode15 upload/download Bug: 1472416 Change-Id: I942abdcfd9fbdc012ff2adf042b41d173722deb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4833277 Commit-Queue: Yue She <yueshe@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:05fe195bf77656743f3daa99d463a794260b429b
1NcxKh1FggudsW2m-k6yEZ_Me2sObodtag7de6Z_D6AC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/mac_toolchain/mac-arm64
[mac_toolchain] Roll mac_toolchain in depot_tools to latest version Added more functionality to support Xcode15 upload/download Bug: 1472416 Change-Id: I942abdcfd9fbdc012ff2adf042b41d173722deb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4833277 Commit-Queue: Yue She <yueshe@google.com> Reviewed-by: Chan Li <chanli@chromium.org>
2 years ago
git_revision:05fe195bf77656743f3daa99d463a794260b429b
maNrol9N_NRlbWSCnjpV7aQMBfxoBEhtoCeCW6ORpOAC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-386
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
SLJcDJyN1t5BR8szKiRDw39W9YOun1Bfzig0uBImW0YC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-amd64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
A882JTDDbItEuRH8t9gFx9Pq8uOfpIMl5eAim3Ze_oQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
BABpEN_EmifauxYOkiOpVttYeatWaPnSry7RmR28a0gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-armv6l
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
cyHtQ7iqXUDicPoBp1_3MeqzHymU2gSq1L0HUAFzp6IC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
tI3j6aBFXgzODwi6b6eJmjSCgfcCqBYvRwjlUpS4WrAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64le
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
YSfkEbA1Xx6nxGqw-VQtIcznnDk1ren9NWl47YgieycC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mipsle
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
eP9TrN_x5dtgf5lzizrs7tH3F4Ha0nkCxO4RBMazKLoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
6bgBO5Snel2Gh_kXd0Xmm8LjLNKCwyLz-b8Jk0z_jYcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64le
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
Z3f6vtVnTsLD_Az1zZlyh-fxZf5Ktiq_zQSrZNPudaEC
infra/tools/prpc/linux-riscv64
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
ViGe-nRNBp3uX-4_yv-_L2bSWr3_PLtvExEm9ZCdbQUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-s390x
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
GI-ec477TiZj_qKq8TnaTQHTd7mNg1HIa6sRsiKvT98C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/mac-amd64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
L5auRzn91XQg-yZgF1rcKgDNNFoyXRgcrBcT8CyFPxwC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/prpc/mac-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
8BYgb-Cf84StNfoaBYY4ewI4U8N1db-xOY72PqXUuJkC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/windows-amd64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
yyuRRM4hxE92TMqkRcb_kteWfro6Plt3u7opJFufS68C
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/prpc/windows-arm64
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
git_revision:bd3a982ae62b4820b71414b2340e86019a1fbd26
iFQvbmYSkL_IlmJkH5P21k3_-xKFRe4pshtZbH-k7dsC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/linux-386
[Depot tools] Roll rdb to 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
2uPJ05EvIYs8fidnSS3KuS1IGW0aI9mWw81Rcjd2YzgC
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
RTTxnTz_TUBSsINg5QEZNhQ91jvFwK5lXxQWe0tdu58C
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
UIVhYM0NUR-6no72yxPdxz4l0AohIZeDwo8xbv3hupoC
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
JgliYH0q4EPwHw6BVziJiUBBCGDF9rASHcMFmsNYTccC
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
qEA28L1Y3OxSaNvDW42QZSdiB0g2w_HfQqbip4qFX4wC
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
jdjU-Vx5wNrNmIIx7AgIPlryVvs8-Qtln1moLOJ4YekC
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
wQTpq_TjozRvJ-K4DhP2UuEcGw7Sn-MLiVIzQKmPgJ4C
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
Y5HwcYyH-fMBmheEw4P8a1bqbRHqB-dGAyxkiFIsHa8C
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
brlY_1cxe1Odw1ZskSbGKn-XVoxxK6mjGr4H_Hep0QQC
Roll packages to make linux-riscv64 available. Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1138584 Bug: https://github.com/dart-lang/sdk/issues/48545 Change-Id: Ibcd10ce402abc8d3d4b3e6e2c045be9c97fb5c0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5076225 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 year ago
infra/tools/rdb/linux-riscv64
[Depot tools] Roll rdb to 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
0AvBFO8AIm7UNMQyWM2cqUSVLgX2JPTWISq3g_FEHV0C
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
mbWf1py8xvqkpPgd1Vsk3lP0ryROW9a7xZuygaDw90IC
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
PnqccdrnZXOlr-Sm1UghsmOnoePwAqXoeW-OAbIUgSMC
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
ldyKFLyYr8PAFd_WSSGD8g-sclsj3Pts9nY-i2bCzyYC
[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 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
hyqH8VH-BR08_zzYmAWR8JkH_5oaUaRUE9ijKKzxUZkC
Roll all tools to versions that are built for windows-arm64. git 1.39.0 was previously rolled to manifest_bleeding_edge in https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4149950 and is now being rolled to all users. Change-Id: I4c7a3bc60e6b3b2625cee59138235d398adb27c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4159755 Reviewed-by: Josip Sokcevic <sokcevic@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Brian Ryner <bryner@google.com>
2 years ago
infra/tools/rdb/windows-arm64
[Depot tools] Roll rdb to 6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Include https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5555500 via https://chromium.googlesource.com/infra/infra/+/6dc7eeb1a5db99a04b6ee701fa3b369813528c20 Regenerate cipd_manifest.versions using `cipd ensure-file-resolve -ensure-file ./cipd_manifest.txt` Bug:b/341607007 Change-Id: I05a5f38db85b2ae00f64d5ae94e940e74be458aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5556722 Commit-Queue: Tuan Nguyen <nqmtuan@google.com> Reviewed-by: Chenlin Fan <fancl@chromium.org>
9 months ago
git_revision:6dc7eeb1a5db99a04b6ee701fa3b369813528c20
XRdxnkP-KLgDZfQcsNJut7B8v96TxsHLERX4bOIXabQC