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

495 lines
16 KiB
Plaintext
Raw Normal View History Unescape Escape

[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
# This file is auto-generated by 'cipd ensure-file-resolve'.
# Do not modify manually. All changes will be overwritten.
Add crosjobs to cipd_manifest BUG=chromium:973247 Change-Id: I8be6386fc3ab9ce6e8d9558862dfd0a7c74a5e6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1743018 Commit-Queue: Yaakov Shaul <yshaul@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
6 years ago
chromiumos/infra/crosjobs/linux-amd64
git_revision:ed616d595eb7241d39d34907050d2949121d6ae8
_vAeU0Q9lAxn933K8vDhwGK40zKVvV-yXGpIy43ATXAC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-386
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
7T0PR8wcLZtBiWUOf6Jid9CDfXrNid30AAcNRGeyVmsC
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
17OpjvDqECH47sqY8YQPzVEraY-0arvSiLc2lG9jazEC
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
FomCUNqE-AG9fmT5C_AbYto_2aDB4KZP2JJJPSLD9EAC
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
HGg8XeIrIl8k6vfzdgJhxTeHqzl2mI7d49s23_y1fk8C
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
7st5GKTdokF8JWVFxnulprZPx2Bd6aswFGpNfW6HGCAC
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
pZjN0Df2nlhHPk52vl4qje47dYO_DTXRlw8fRaU13kcC
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
r23Wz-akUSGD7Z8DmXfGYfyQpCvBUpbhPg35NLJ9y8YC
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
V_bh35D0JtTiankDwWg4pdrxQI1qcsB94Nqsm1HFXGIC
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
26jFo_a8A5DTRRZnTELcL9Pr8X1XzVo-U4AF_7ucJZoC
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
7L7w1bMeBx-UgOhO3ad7ixxCopVpSkOWMpHeY2Hxoh0C
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
kzMgc1cvpargmFHjVgTAkFI7G8Y1tIJlyE6aG-_Bw3IC
[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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
L7KSqaThgUwXj2z3_6ryzfw61usMG-UByDVykNlJUZ8C
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
pinpoint: Update Pinpoint CLI This update includes: - Support for job result downloads - Support for job cancellation - Support for waiting for started and ongoing jobs R=dpranke@google.com Bug: chromium:1175615 Change-Id: Ica3617413a24870dad76e7747922aa88794c2e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2732279 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com>
4 years ago
git_revision:3c08bc7f9da8e336a5bc2745504ffe4f0103e39e
pvE2sLLZ1qSTTC4kuU9hvpXh3BJ_ZEqlLz7N3C4l6rMC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/linux-amd64
Roll out new goma client binary VERSION=215 Bug: b/179630263 Change-Id: Iec0fbe3af1c206d9b5ccf5706156c1b7008f3200 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2752426 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
4 years ago
git_revision:f5efece09286e7fab5fe52a77a6f3bd515718ae6
KEe3h9iBuvGK1k_uGq74q0J7Mqs_TDD3tSOQ3hnvkQ4C
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/mac-amd64
Roll out new goma client binary VERSION=215 Bug: b/179630263 Change-Id: Iec0fbe3af1c206d9b5ccf5706156c1b7008f3200 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2752426 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
4 years ago
git_revision:f5efece09286e7fab5fe52a77a6f3bd515718ae6
HlThEKNzLajyWEid11jf3oaA6S9mi78AKO7qDBpH2L8C
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
infra/goma/client/windows-amd64
Roll out new goma client binary VERSION=215 Bug: b/179630263 Change-Id: Iec0fbe3af1c206d9b5ccf5706156c1b7008f3200 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2752426 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
4 years ago
git_revision:f5efece09286e7fab5fe52a77a6f3bd515718ae6
aBpIgkKOyQlS5WayaZEThpfbFSkl2qcdFI7uPY_ZvykC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-386
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
HYYAaSmsnHK4BvV8V99FtSnxCoSwvKNCZdkCmJm0hNQC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
d95o0Gm74HxIxVQQj3hBeKAuQh8qYcHCsnXC8YCT4gYC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
gWR3eIf0gH6UbNDhCfw-3yMyAxyk_XxxQuLCEwA5IkAC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
5eSc1y_n3EptZArzMHa2HzjhUP0hmP8wFhdJf8hzdxYC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
yZZD-2HowMo6wPFCEtGGm0QwLaYVM3A0hEgV2Yt8XcwC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
TQiX13FgrDlAhEV6oWNyM9KLnvb4SCQER-558tjD3i0C
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
XYCGZ-8NvE-EXg6KCBL6GG9pXWas0IDFGVKNQqtRaFsC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
md9egvWG0WwtTSSDUFwWZfNcGH_AA2LpMMHKFQa9xu4C
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
jdAFY_snDVEvDpDxV5HDhRI0ieFfczESruVaVG98ySwC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
XRtve-iXGw7CoVfVrpQLuiV5_BHNrjmTSEoiQK6iCjEC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
D1wS2ZmEeDQALAj6wlOHjY4Mge2Ow1wYQLyHeGAEsGoC
infra/tools/bb/mac-arm64
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
rHhXUD6yTCIeneNwH2vpvKQgHbIaGJ90iB_YComQ_lgC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
luBELxQ6rVbt4xyS_kU3xFvhS3CFr92wp0byfW2-f3sC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
B9tMsIhec3lGlIQhQ6gn2sLxjk_X_W_8k6RPFLtWahUC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
HSTWiNz_VSn9EHoykJfGCDEp3TPdD7fGxjBDYAra0PYC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
QLaVYpk79HizHrkk3Uthk6WWIckbBiPfGBFId0aq45kC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
iCB8PRhr0R19YXS3pkqlllV1slUzRUx93kLSm3cMo68C
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
EwS8xQhPNLdUFHAO74yrlxXdFtiXNPsv12GR3B4BN-YC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
4XzPmt1ngbZchflWlDzPhZPD793Jcb1EXJRBhlN89-cC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-mipsle
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
fz_C9IDwV-8PE8rcVA1jhgNf8oFoqIpeW36rEEZCVBoC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
1uab40HcOgnpMlHo6uEHAAmtmINaTm7_r1MoEa65SqIC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
d8MxLNYzF3zrDIXxeS1Gdc2TL-jzvNBeQ17VG6z5_skC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
Dj8sG0gJjGfKwO7ykL3U1Vv9VLVHgxBf_muya2iIADYC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
zEcXRMBYi8JZx_k5XfFNvt-IxoLDkLtBC-qa1JGodlYC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
Ca0gw6VfGYUnYX6c8fzltA_XI0QhX5p5eV3NNztGOpsC
[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
[dirmd] Roll dirmd To pick up https://chromium-review.googlesource.com/c/infra/infra/+/2757296 https://chromium-review.googlesource.com/c/infra/infra/+/2762697 https://chromium-review.googlesource.com/c/infra/infra/+/2779750 R=sokcevic@google.com Bug: 1179786 Change-Id: I34c2a28d4325a5004e8cc32d6ac74fb2f2fb4390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786133 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Reviewed-by: Josip Sokcevic <sokcevic@google.com>
4 years ago
git_revision:9279002e230abdc26e4f482d44f543dddc087d38
9iuUr0aUUJHM_FOoJwZ0sI9JWe4WWxrH2CWjGAEm22kC
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-386
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
eP17h5YJMrU6hWBOvjZxWCz5h9SgkkW-vVF7W-L9qwIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-amd64
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
Xf6nFp5RbFKQLUk7d3O5LKPmmdnAF8NU4NsoO0QGP1UC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-arm64
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
owOKUdyWr11KyfuCRigGRsBM7uPnOMVrH_WOMYYCGJYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-armv6l
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
iZa8O1smpKFTta3pQVz9TaIOlRIu31V4QPgGbIVkCgYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-mips64
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
s6dXt6MAJ8kreqm79HyghgHg9mk93u8ju303d1RIZ4cC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-mips64le
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
K2S9QpIR4701H7N2E6Fm9iGCOg8hwa3mY51S1CmrwdEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-mipsle
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
0jLzmuxOsRVyYofMKQfgivPZOtxsXv0Slcr1dRU78UgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-ppc64
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
7SK4rFVEOeA4CqHD0mKebTOCx7viE-dJMakFqE6W6BsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-ppc64le
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
ZruNFqBhC_reTL2dw3wf-t17dc_sPZJ_733R6BLBvMsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-s390x
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
8q6NmriGR1GiT9e-UlHeau2VMkcN0UYumU8AVDLIsZMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/mac-amd64
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
pxk-T_GADDuTTtmbUsK3TlMHbsMD8jb5Dt383XPmeeYC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci-auth/mac-arm64
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
cR0PKTchP7f5iIXZdCSffnp_p1_ySee-16Gg56qhxqIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/windows-amd64
Update luci-auth tool. To pick up ID tokens support in `luci-auth context`. R=tandrii@chromium.org Change-Id: Ia2fc9cac96256bdd74186dcf584a47bfd97f7a0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2780632 Auto-Submit: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:297491c0babda68d84d8240c9d4504be671bc804
McEKBb2FM2gMj1og3guOfA_jd690eGivhdSbKP90ruwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-386
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
URNSUWaPvgkShVa1KnmAtoL5azW--NJQIznYqMqJsAsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
arYTWbSh0C6lD_sK_kJz2-0cZY_OhQmrn5in49biwiIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
oeVqY9SkMvgpT3i5SZR8UTxGem0jBmUBO38A7r_xelwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
KP9zXh4xaBORwkbQ3SQgllrhgI1mlsY8kkLK6lsnQ6YC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
dM81VMaSFTGT6Y0J7SMKVkEj5slPcjPOXZViume-EBEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
NyJLdeAtnCXn1xtiP-uya0xTRS4tFlHgDN5ta9abhBwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
98hERW5iHex2Ayz6sJTYgF_zOJaWhWWvGelswsIjpR0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
OignQzQH5fIxDHPYKZmG7VnEdl3Z94ZiD4iuF6er3AMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
4coaCH4ckQX7J33o3WykAPSGkiOafxUqK673YytMPrAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
Ve3gsDX8mBVAlUQ0h-5i78zblyvA33sQzCKQtneeyMYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
4G7W0ODHFwvftRI3J3LSeOeK73E2eTF7fQr-nGK-TW0C
infra/tools/luci/led/mac-arm64
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
EMB0seZ_Mxl01SvYptP_gBsSoPCnQeUVZA7IEYOzvusC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
CM6tNbvHbG4E_N-UMN-YGmiSewH3KU4aIPaKEeRyCjYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-386
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
Y8Ek36y7b22QsNhnCMSXwR7QpNbNVQi5lX1i3b7KRKMC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-amd64
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
YxcAZcBh1UCNZjRNvtSfo9vgtKLbMD5P5I9nbmw0--EC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-arm64
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
iHVo6ANvfusz5ckKkxWu_NpYflFNf02fdiN9f3ZoBkEC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-armv6l
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
es1tnfFnPuHE_0vhfJPGwmHmSNAAKFE0xnNuijmgpAMC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
S9g4y0I8CqUEE1iAXk9w0xL4j3skjxKTdcTGRw1F2AUC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64le
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
jBaTODjx6l4rHLXTVo8Djev53TdNDTeX8vnMKmc-H2EC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mipsle
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
e_rqrr_nkUB8Fq3EGnNPX2pMNJOQhi8lTVBJ_B2dLyAC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
lFPd6KlRl4zMVjNXqUFEI0TJAFIZNerxdwfhUsvRHeoC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64le
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
ktGPyKeEArzhIgCe_pKn-oWlY418iKZ79UvUOU7dMIYC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-s390x
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
u6AIOEDa7ON8bev9c0Z4fhEv6nU2jX5xG-in-Fsa0LwC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/mac-amd64
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
io5xlWMHJlMlHjj7IXSsBgRmWcq62Rd3BTnryGkB6U8C
[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
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
MOOImqx3de3lit0Oo6u1BvWeIKJp4WgcsctyBhc4a3oC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/windows-amd64
Update lucicfg v1.23.1 -> v1.23.3. To pick up: * https://crrev.com/c/2782857 * https://crrev.com/c/2783876 R=qyearsley, tandrii Bug: 1190367,1189795 Change-Id: Ia31c427f2a77aa24dc4ac3201db7f4012f903d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2786281 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:d759c61ccfabc12e0da549ccc25aa8bfdaf37615
fGTX4AKfieWa9pZM2mjcEppEVnYZgQnXPeIWhe2NTxEC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-386
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
2ruKSm1VF5rRMSQs8QpnQJDEVjvmDf_QjK6f0lfX7ecC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-amd64
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
4wgGcwE-qbz1L7FAqp2Sl7BFQ12fLTHUjQfMG6vIP_kC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-arm64
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
mQqeVAXponWeGV3pO1qBONt6p1pwMAMdWUx3cEqCK2gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-armv6l
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
CExmUu7q4mkcknQUkU1UWJ5vYcl5H7OV977r9UFZWcoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
7V2J7__lxjjF_nWO5uvN5mquCsmo5KPEFNVnQhOFTmcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64le
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
tuooVoVP6VEUY14Wx-btJwQN5fgSjIq1DopXiFbMQ1sC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mipsle
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
7NGflC_Sdl6uWq4pLx4Noho208zc0uKZ4hedAHwqGbEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
trAK_mT97Th9c3Z3RNqRgZERqn-R6rDGKRVJ_9PRPT8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64le
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
NBhpFMIXgTkg1fYjWCVMZys6O_32nANW_WxY_drrLEAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-s390x
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
Bk36BhXxXAJ4k0WQYXKXP5XmTU2C2hMOORyN6Gxn6msC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/mac-amd64
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
RgLsjwuofDcDILewynEfuiQqERiawSOrp2n1oSz5ASkC
infra/tools/luci/vpython/mac-arm64
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
l-R1IIcoskcFcLsMYK4ZtAr0gLbpw2bZ3SFNcwzCHt0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/windows-amd64
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
yZ43k64yE6PS84BCPjxw4ZMEXZzzkxuBA9t9ZwesgIMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
Roll mac_toolchain to latest version in depot_tools To include recent changes: - crrev/c/2680852 : Ensure Xcode.app intact at installing. - crrev/c/2676139 : Do not upload iOS simulator runtimes for Mac. Bug: 1064615 Change-Id: I9874c7b3664dd20745a772d52a682e552e6c0af8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2689105 Auto-Submit: Zhaoyang Li <zhaoyangli@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
5 years ago
jG64q5ZTG9M9pCrAtrc7U-OnlnHBT-R-tlzpoH5Ac0kC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
c7zREjzvqW-OWtk7lA6EKb67ZmsziuMrUjN0ZulQ-L0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-386
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
NMhFUzejvjQIiV5bmMPGlmh22AR3lvg6_LnqCxVs90oC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-amd64
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
W-1qNoaEoIMoLQZiwIi3Mniiirl6w6SmPbLMrG6qR7IC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-arm64
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
_TJP_DSBvKBLRsELGo1pE4ACmcHVC-g8Ay4Z76oMF48C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-armv6l
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
c32yDGBnO-_nuY01PPb0BmFD3mTrHnGIW-1gJGhOlmwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
EC6VSGPEk-1jIrNKeJmwpXlEN_7-TbzXysgyn13oSBoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64le
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
tAUa8HKCYSxuJGsyn7AZgbj4h2_PIvUxqcHWprK3gkcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mipsle
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
eYrdMuDBUiypBxOHbeFXW6biRRUaQTuFG4x6qMpvrWIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
Lpa6yMxnDgH3ZsxkzKrUKbUwikvZFpBs8VvsqmgiitcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64le
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
XEDr7UcCP9ZaYD0JaajPIIUbDuGdUu9t5HCKkKTX01MC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-s390x
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
WHhHSan56GNtiuqRFPxsvh8NOJVbiC8pu9IdTru-5b0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/mac-amd64
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
L53gVrGaRNpYo2cEWTfZO4JMet8e1LNMlkNIYQKGSEAC
infra/tools/prpc/mac-arm64
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
63ICGLS_pq0YLXo0gljqa0LqHa37T8K_mCSJ37UkweQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/windows-amd64
[cipd] Update 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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
6Oa6Qp8os-roqwHgFdTaA0vlYp_ub6gSPA6Nmo-R9zwC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
g2nW1jgOwccS8k-NnhuH0_EtE4rnOLwoPbCX1WRKSrAC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
WGj2cWQY1fzivMoP6P-Z1LsA0UgOXyink3SYXxiJngcC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
dMNHdI0sonWcGP-KbB3fl6HaVMoMB1tU-j2er1j3adwC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
DJKX14vRXnWaVqNHTw8FRc0sh7uid5wAlMn6fQWQdKUC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
mknoduEoLNKV8haLaqW1RLLje-vDh-pxSv9pvNxaJ88C
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
2fgE_fYfHDQ5XGQeFjqBcINrn3z9JkAiZ83F-bVdhQUC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
48lxT7Uil-gZm2NRlacpxKiGaQ9tOR7lczNmGDLkiswC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
sly74_9_CZUqepW-70eOciwSy-U4hZifmo8AoVjSKmcC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
P9t2RSHXL9U6imVkSt0xV2ESgYN-TVw6p0PnygQrShUC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
dvg9ty_dryRtQsIiEtByicRxmLLjwkTDHmOEkLRAp_EC
[resultdb] Add rdb to depot_tools Deploy rdb in depot_tools. It can be used to stream local test results and query results from the server. Change-Id: Ic2fe65952d24b79edd98bedb678ee220b165fef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2176997 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
5 years ago
infra/tools/rdb/mac-amd64
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
-F0XksvQrPA6j1Zl4pnksFDIDqWXsRpvX3jtQJWseZ8C
infra/tools/rdb/mac-arm64
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
vE1wc3Zla6JnCK-s75yeLICLHBnzkqA_OyWm18RdzUIC
[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
[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
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
cNMPVk08E3I8FxubmTcAFOJOlBerzUS3r8-0E6-ZH5oC