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

499 lines
16 KiB
Plaintext
Raw Normal View History Unescape Escape

[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
# This file is auto-generated by 'cipd ensure-file-resolve'.
# Do not modify manually. All changes will be overwritten.
Add crosjobs to cipd_manifest BUG=chromium:973247 Change-Id: I8be6386fc3ab9ce6e8d9558862dfd0a7c74a5e6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1743018 Commit-Queue: Yaakov Shaul <yshaul@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
6 years ago
chromiumos/infra/crosjobs/linux-amd64
git_revision:ed616d595eb7241d39d34907050d2949121d6ae8
_vAeU0Q9lAxn933K8vDhwGK40zKVvV-yXGpIy43ATXAC
chromeperf: Distribute the Pinpoint CLI This is an early version of the `pinpoint` client for starting Telemetry A/B experiments. R=nodir@chromium.org Change-Id: Iff11f8a16f93172cf71d9f76b02c27bd3b659111 Bug: chromium:1175615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2703000 Auto-Submit: Dean Berris <dberris@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com>
4 years ago
infra/chromeperf/pinpoint/linux-386
pinpoint: Update Pinpoint CLI This change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
jTBoVdnBtNT81MCMeLUKNyMH-3NnfcebVYsveUiYji0C
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
OqLpAw1j4lMJLE3KNv8Mte3_arHlHmvkKCMTbWA6WlcC
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
djaQQTQgjPC3KxIIkXWK4HTdkdx3cVP0UJJQ0yzchO4C
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
mBJ8f4hcmR4eQoGitcJSbP1xYe5x2bf981cXurZ1mZYC
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
QMtnuQiJU8zqgIB8_Kaox-MBljx5dAz1uCj62WsCeNsC
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
8X9qDF6khuTqlCI7HSn1ka6eMmENQgISXBAphjvfeFIC
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
uH5tlJAVS7tEKICwqkXTOENkuU7ER_GonzvM1elvuLYC
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
x1bnTHoEcg_fQtj8MKlrTVAFsan_FyHRN52kGCyDxu4C
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
DgYPLy3rFwP9tW7ePA0B809IH5YEipTXbVXi5b15v28C
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
7YxiKb4gxplTZs39czfqZcjJM_u6puS764qc34JYXywC
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
Ukgn0Jgww3JsLVwXA7seYmfXWITLNTDg6-a8XEDGS0wC
[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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
YelBMPrKeFrye8D0cfGyxxQXPPqplZW0xiH7syVZzXIC
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 change includes the following commits from the infra/infra repository: $ git log --format='%h %s (%ae)' \ 97ee9cecaac4d99be09278169f987e61b8116672..HEAD \ -- go/src/infra/chromeperf/pinpoint/cli dabbed3140 pinpoint: Add support for experiment presets (dberris@google.com) 2c16cdc58a pinpoint: Initial support for user configurations (dberris@google.com) R=dpranke@google.com Change-Id: I0bb7a5a167e57b64d8328f497386d5b68f3e4a22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2862344 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:dabbed3140678eeae59dec3e48d36db396a0a9a7
MLqBgkm8N4q-u79jxz7sjtWDXChgiNUqbZL1GAxpsPkC
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=219 Bug: b/185543547 Change-Id: Ide2f77ee37f3d650a9c5a5054ed962db5dda3d22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856514 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
4 years ago
git_revision:eb2e76c81f2216fe8b5dbcffef291664cedf26fc
REvbrBLj1XujtwAugXBsjR55A4qsRoQE61RSG2YSh-0C
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=219 Bug: b/185543547 Change-Id: Ide2f77ee37f3d650a9c5a5054ed962db5dda3d22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856514 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
4 years ago
git_revision:eb2e76c81f2216fe8b5dbcffef291664cedf26fc
z-6A6ehbs4uEgiPrRMCF0LwKeQtAa0mMG-Ub4CjqzRUC
Roll out new goma client binary VERSION=216 Add mac-arm64 platform to provide goma client on fully supported platforms Bug: b/182514677, b/183118231 Change-Id: Iae7581883d403a1a28f7d0bb1b871c9cfd0f7e65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2816481 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@google.com> Commit-Queue: Fumitoshi Ukai <ukai@google.com>
4 years ago
infra/goma/client/mac-arm64
Roll out new goma client binary VERSION=219 Bug: b/185543547 Change-Id: Ide2f77ee37f3d650a9c5a5054ed962db5dda3d22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856514 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
4 years ago
git_revision:eb2e76c81f2216fe8b5dbcffef291664cedf26fc
fuYtD2NCy6kY0uSvDU1-EJLEhVjcNA6IYrKzV5bhFl4C
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=219 Bug: b/185543547 Change-Id: Ide2f77ee37f3d650a9c5a5054ed962db5dda3d22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856514 Reviewed-by: Fumitoshi Ukai <ukai@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
4 years ago
git_revision:eb2e76c81f2216fe8b5dbcffef291664cedf26fc
5qmT8lvfd6IozXse9QpoHGZPuItg9c8ICzWb41MNdDcC
Reland "put goma client in depot_tools" This reverts commit a0aed87f71211aff48e3c06802d173cdf21328cf. Reason for revert: install goma client without update_hook update_hook would disrupt current users, so start without update_hook, which means goma cient in depot_tools user might need to restart compiler_proxy manually when updated. https://docs.google.com/document/d/1pnwfkU6Rd9dRtQC0sg2vATmyRbkYWhnNUTD5k1PddC0/edit# Original change's description: > Revert "put goma client in depot_tools" > > This reverts commit 77780358011f8e20c68ba10aa1282f1f9f65734f. > > Reason for revert: AttributeError: 'GomaEnvPosix' object has no attribute 'RestartCompilerProxy' > > Original change's description: > > put goma client in depot_tools > > > > install goma client cipd package in depot_tools. > > > > should not use $MYPATH/goma_ctl in cipd_bin_setup > > since $MYPATH/goma_ctl uses cipd_bin_setup in itself, > > so causing recursive calls. > > invoke python to run .cipd/goma_ctl.py in cipd_bin_setup > > instead. > > > > Bug: b/77663154 > > Change-Id: I9f82c766a886a2acfb899e3594e5f05a7b7bc75a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1866350 > > Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> > > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> > > TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com > > Change-Id: Ie050dfb524dd885634c31be829d733613e80aece > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: b/77663154 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1872129 > Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> > Commit-Queue: Fumitoshi Ukai <ukai@chromium.org> TBR=sque@chromium.org,ukai@chromium.org,yyanagisawa@google.com,vadimsh@chromium.org,dpranke@chromium.org,tikuta@chromium.org,ehmaldonado@chromium.org,yekuang@google.com Bug: b/77663154 Change-Id: I8bb51631e4418ff63953099814bdb464128eb279 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1875982 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
6 years ago
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-386
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
nfuWcouxLXZ_QVTBQzTYeBclxdmbEP978PMBcu6D2YEC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-amd64
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
ukfK0rEDJnHssVOzMJQjXyJ_wMGaonJw_jDB_xP1HsYC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-arm64
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
FwjZxkgPOcSr4yUSJvuAx2dLI967HjkYL392NmQcLKQC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-armv6l
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
Ge7N8w-FrbE4TZCDfg53f-ZvqnEIo-pOjZYG5QrZGeEC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-mips64
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
DzcJgGarfTYpoV8_i6w2857RVQJtC802WovJk6QDonUC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-mips64le
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
b-ei3R_nxMcOWg2pzGYXSFA0S6rZXcBW8wWELConZ0IC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-mipsle
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
9k95gMDhSZlc8m754MyTM5EF25GR8GxUcrEhTjzbS0UC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-ppc64
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
bJg0fWoBWyWkgR2xy6kPAz_LhcQ9wCcAEdjbESSnRZ0C
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-ppc64le
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
7RJpQpPnhYsZGqyKN1NK4hQST2HO_X9qY6AVvQD1B6UC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/linux-s390x
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
lMzl9b9o_T9HwNoVIDV_yT-39D7iot0OTFLhgScQ7_sC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/mac-amd64
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
BGLhCtjzuucq3hS6L7Cb8WU-1r90a9RzY-gzAcpEJcEC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/bb/mac-arm64
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
DC9rpnYPFvhpYsR5duBtPYfpNattWUfpcA4h9sxanHcC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
infra/tools/bb/windows-amd64
Update `bb` tool with enhanced support for experiments. Relevant changes: 6a6825419 [bb] Add explicit experiment support to `bb ls`. bccb58660 [bb] Make `bb get` print experiments. 0d2672023 [buildbucket/bb] Add the ability to set/block experiments in `bb add`. 2fa412040 remove is_luci property R=gavinmak@google.com, vadimsh, yiwzhang Bug: 1093970,1134774 Change-Id: I2860857cb86626ad235dbb87eccf19ed38800557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2809195 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
4 years ago
git_revision:1563088c23532d1e45b8c3041afb9458c1788fc3
B__VpnkTIRXnZyy1hueecfk78ZCZEBIQV2bgMn-ZIooC
[bb] Deploy bb Add bb to depot_tools Bug: 946422 Change-Id: I7f1e5463b7bb1170124c94066b660a1b972884bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1550200 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
6 years ago
[dirmd] Deploy dirmd Deploy dirmd tool via CIPD. Bug: 1104246 Change-Id: I3681262192c2eaf706867d3c49a6293171c93d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2298244 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
infra/tools/dirmd/linux-386
[dirmd] roll dirmd To include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
SJ0WZTj7bENc3wxKx2FwLeChYjPWW-h8ZXccseKKoXUC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
X4YQERXASA7MDmlC0FC7NKYQx6aDokbob0pLvx_46RAC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
0eJs7c8HvgTuyb-XBeAvPeMMyHABhrusJo6zJWSxyTMC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
x9cFs5znQVbsXs9SLMrktqbUn0ML-WANQOM4u7BVutsC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
-rp2QLvL3e8nnRE2xbYYAKcHqVtmpduGc6Xi7WlyI2UC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
yH-Oz4IqPRsZpL_6s3jgDjXCTH9uAqLldoZNSt731BsC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
a8Yy8E6DsZ7AfUwRlnRfsOHU_tBEZ9C9PYGLsZWxM3cC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
jRfsUS7y9r0VuZIl225ZWTG_MuJzS_WBPqOgg5_YYhMC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
i1bFnWKDlh8E3K0ToZJBtevnLRqsZ8VmZxxAEvouuisC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
eZr0_InCDL8oK_aRv97dbjJT4MJSHO8vNll0d8vAnC0C
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
7vCkmFH4G_2_99BJty2iV87zA5cLJTaLr_sPtpt0WmkC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
OgZvMtYzIU_8FQuU6iLGRuob2LI5eqRXiYFTKupL-yMC
[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 include https://chromium-review.googlesource.com/c/infra/infra/+/2815945 Change-Id: I74dcb46948700b02bffb867fd1ff51baa3979d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2818896 Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
4 years ago
git_revision:c7072c98f7ac3ce1998542cc5637bdc54f908f4a
5DW2qtuhJZFEhcQGEKuN_Cq20rwMbBagUsRmc5zMrGoC
[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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
_8H8TQwGp0KIZTzgKeRuvv7NjIo7A0hIGF32yrK5mNUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
R-C6dnKZ61pZPQB16jjl6K7rnlZLs3tXTxs8HpoyFsEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
ykAwMJ_9KW_Y8hZ5SanqsHBTAkUxdmOsSn0FUB7dfckC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
As0cbh25bdnmfsJ6klXd4y0WkxNycO_zSDlAOZxrQMEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
bifGVY5WrXbIWXnG0cHUWnq9CkCVJF9v8DbE7o7u9LIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
EBGYBWUrCOEIQQSTanSRaatD-VSpzZ0NrcfUBOOQTFgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
9bMyRk4hbqXWN0wFBge-qXM0C81boPr7nJ81Rbx0SKcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
FHZDrKGTbLO2Ru8AoEWyXQNugzlAEZkEJWPuV_xvE7gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
2G55YC5otjujI5keBq50x-0nLvq_LYh0XDyvRpUZxT0C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
nfRsXr-cFW0lwANNgff_CV4y4rW-q3bKaVdfhSlknJcC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
9H8TMc73UtOoBG7PoqjSJkSv8wwjY5FXps9vteqx3QAC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/led/mac-arm64
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
MXv_cP08DBNNbfgTyPHrgTTg4kKwGGLOJ_sEiGTNx3EC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
update led This is to have the latest version of underlying library. Bug: 1200494 Change-Id: I43f1628280e75b94b21c2c6a399f55a12970252c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2838848 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
git_revision:bf50da1e65ab2c894f9341913f8b6a9906f29285
xF1p50z4t13Y3QmWhfz4wM7BtsHatgpL31aZ8RicByYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
EmoPiwG6uXI71jLIu3Tm2ELLR03rUN7WZnEYxSjDpAkC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
PMtYQZjwjCpg20bACL3_jgslZ0H8MYPyujm7275q8wUC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
QMU4ZkSgEmcclyuebhzwaBW246T1rW7MwjBb6AwxJegC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
rK5w2B9mlqb8_2EAzWK2bJwq-vLwDapPr4o4HBtjl7IC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
o3qjeZ6yzi-amz7H8qsg7YgynG3iUhCxHpLi5WlDNjUC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
QInkNEr6XQ5p9_DZso3HwdpTVagkhnp_UdyY7mzhfp0C
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
lUyvhT_zzyWbJxbicFp1YlvEm0dKKfo8ygOr52S8YFIC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
-viOY85EsBRfnfH5ZiC1S8sKerLE1aO0zCTCgSkHl1UC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
vRwVXpBfhZFziX27v9CRY1akcv7fLZPInHLCI8JRK2sC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
KqMLswQKx5_etRyuapkbWeO8Kz54Hh6cwtt7rZ63rLEC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
Atkgj-ow6pPBF5s_I6eTRTVQ2mE44EN-TavYrX8BzBsC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/lucicfg/mac-arm64
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
OJf_fogc8UwsQfFfmB115rnISPBeJGtopN-cw2IPtOoC
[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
roll lucicfg to v1.24.1 To pickup support for generating tricium config and introducing mode_allowlist R=qyearsley, tandrii Bug: 1194244 Change-Id: I16a8792e8d4df4127c1d545dca246058c8f93066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2856909 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
4 years ago
git_revision:39125f56fa65e567ae46f6297ee5d6d88e3fc0c2
OOg-D3L3ET5CIvMxdCkRltIM7Ajg6_V6AVYKDmx8514C
[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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
FWfDv3lgODByM6D5xTaSmKW0lKr9-qoeY3ycfqZEjwYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
ylfUAtNGq6VyOkRcM6vgHxarlnxq5xWZxG6Z57Q5iIsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
7wVUTQeQO8LIApdCV6jPQmSEl_nySK0mNI6-2FBTqL4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
nKUX03ClKeT4DsB8AxsIc3hwI-XDXeF-y35yFqLHFSMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
oL6G_yMD3n6KZr2C389Qx0WJfdYtORSXMov8t3LFf8UC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
n6sn8iQk9eycREQyYRG6KQxam_S6rubYRt7ibV4VbEwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
mlulTx5yajKzTQShDb5El8H88kRPYn2UU6XgkaU5D8gC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
5P3M_wQJx1YKQ8Bjs7kHgJAsX9Lq-Zs3fkg-ovQRBBMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
XLY3V96XlYury3KL0AnusoRvFUNWNnPVNgVNk-5aDbYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
o-aQg9FUBhhjfLGva1Emcm_Jk-ps9kELYZ3ZCZrpQlsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
lHDbMnCdgqqV5hXs5RxtTef8ROt46R9ZijwA7DvbbBgC
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/luci/vpython/mac-arm64
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
gWicPFdYc5cq_n4M6IQTsJRs6Ffr74NVwgPZ7tZnPssC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
[vpython] Update to 58604ec32e265 This contains two CLs of interest: * https://crrev.com/c/2807199, which strips the 'm' ABI tag and fixes https://crbug.com/1187476 * https://crrev.com/c/2820342, which generalises the Python 3 tag logic to more than just 3.8 Bug: 1187476,1176014 Change-Id: I2138e9a7b2147c8c72cb99daa08642919a30708c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2823254 Auto-Submit: Owen Rodley <orodley@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 years ago
git_revision:58604ec32e265e944f8faad6953489d2d5f0a82b
GPjkFs-PDg2uFx0wKTr7VWDS60kp5DXlvShsc1trVdsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
4 years ago
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
-F0XksvQrPA6j1Zl4pnksFDIDqWXsRpvX3jtQJWseZ8C
[cipd] Update all packages to versions that have mac-arm64 variant. All packages except mac-amd64 ones are built with go1.16. mac-amd64 are built with go1.15, to preserve OSX 10.10/10.11 compatibility. Note that we still use mac-amd64 even on arm64 OSX, since the bootstrap script still installs mac-amd64 version of CIPD. R=iannucci@chromium.org, tandrii@chromium.org BUG=1102967 Change-Id: I8fdb27397fbbf238fe39e81305d4642a0500ab33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2699690 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
4 years ago
infra/tools/rdb/mac-arm64
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
4 years ago
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
Revert "[resultdb] move cipd pin of rdb to enable BatchArtifactsUpload" This reverts commit 90aee2acaff9c313f5c19707a1c3ec142c25f0bf. Reason for revert: the new rdb caused blink web tests to fail Original change's description: > [resultdb] move cipd pin of rdb to enable BatchArtifactsUpload > > This is to deploy the changes of crbug.com/1149662, which enables > batch-uploading for artifacts in ResultSink. > > Bug: 1149662 > Change-Id: Id4845fd421065cfc45442e16f5d41d0001818968 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2850389 > Reviewed-by: Andrii Shyshkalov <tandrii@google.com> > Reviewed-by: Chan Li <chanli@chromium.org> > Commit-Queue: Scott Lee <ddoman@chromium.org> Bug: 1149662 Change-Id: I7b3e5b5fae3e6262134582c0f002ff46065a9eb4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2852455 Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org>
4 years ago
git_revision:e75c9bf286fbb31347379cb478df2a556ab185b1
cNMPVk08E3I8FxubmTcAFOJOlBerzUS3r8-0E6-ZH5oC