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

439 lines
14 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
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=209 Bug: b/173566348 Change-Id: I175386edb044197af00ee78f78003576d176873e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2561706 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
5 years ago
git_revision:9c15a8cecf525a4fbc7d4a11685e7dbd61cdc830
rRJyxXiFVaHOg8R86QGi8oaQPkpRsrKZTTaGlSGwL74C
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=209 Bug: b/173566348 Change-Id: I175386edb044197af00ee78f78003576d176873e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2561706 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
5 years ago
git_revision:9c15a8cecf525a4fbc7d4a11685e7dbd61cdc830
XumiZB3Q8FxGsNaB2HggD6mw6Q18EQl3Nsw1c_ouSMoC
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=209 Bug: b/173566348 Change-Id: I175386edb044197af00ee78f78003576d176873e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2561706 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
5 years ago
git_revision:9c15a8cecf525a4fbc7d4a11685e7dbd61cdc830
vybPXioIlJrr4tLj5CyhZGr970TxZGebPd_mQk4MXWIC
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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
MLh6ReKp-gfyWBVXjOdzbAe5fq6_LkCkRYeMk_fNPOsC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
0HSBCLUs3fmBqrIcieWgcmJ4-_daUhOHpqlYMHsQ9DQC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
A0ZFG0Vorxh3ghhUdeD8sA8dEMaNqymsMAntePkk_aAC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
PZnvslTRV59rXrHauo_qb3EyTGmQQgCAadpbtI87_6kC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
S6Z2b7pugPJQ0BQLEpn86lbgLxkz6ZQ8qGlJnkzP5RkC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
AzbZxBz0-tF6ePl1cqVz9KaQSplwrBQI5HrfcxBGFRgC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
aZfjRNm_GWaKYfbhW3Eini9VSWXexyLlohqe251zGuIC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
PCbj3yL0LL-WEwSOaaU_IYLkafVGG4uy1DsPukM02XUC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
aieEc3tYyiRvJsULR0gVCyaHp1wjclqlQ-VxTPq84KYC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
HxAq4ctkn8I5DbbDpRotVK0hq96bTMfV548E0AuKrSEC
[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
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
JwvL67UwJvjAphFM7gUjJ1yQTomQwACTpcu1UxH7Kg4C
[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
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
infra/tools/bb/windows-386
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
kG8Fmzn7ZmvJTwHitx0KCeJUjbXmB5vcjdz083I4W3gC
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@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/windows-amd64
Roll bb tool from @616b3dd to @165c851 infra/infra change log: https://chromium.googlesource.com/infra/infra/+log/616b3dd..165c851/ luci-go change log: https://chromium.googlesource.com/infra/luci/luci-go/+log/d1ad596..b0d1c819 Change-Id: Ifdb35266d0d1714e42120529ec803e6964f96969 Bug: 1093824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2274873 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 years ago
git_revision:165c851a5838dd48e66240a0de3da872b4b31d01
UN8p616-kb_iyjOwoBcKAHGIam0vWj6ZmcvFXUi_rfQC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
SyhVz0AXVDCYLlTeLtIJXkmKNfEgDyntRp2eA2EOSGcC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
6bMMEZEIuZgYlnghtNqRMqwWCnS1i7I0-t0Mn0ZEeakC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
cC6oG7VcW577jMWfWzAv8qAgGmOzNk7_8VQSa4DSsNgC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
NLiH1AIJHsQjJOkMZhwC1qFUC0QvI2v-0-kijs_AJV0C
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
nUWJVxz3dzNvaiBfKgc6h22z77l5nBy5Iwjpfce45foC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
CGsWiczO49TByrm_puC-p7AmhiIhXMdNCigzVMBQz04C
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
2Teh8pqsm5-rRxB0Uj6J3SJvY9_-mSDpQDcKzQ2PENkC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
GiByHMBUCWT-yDkLEWIBvG4OxL6zjplDeVb-qy_2wvQC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
tBHCXJoOLDOVcEm03_nuei53OOPM8JcrrFd8kbXCgSYC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
GBtRNFxHKEQWW7JMskDR2Qh0G2KOFWxP2iqWFLWrF-MC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
nEbvXYgLq2PvRQGvFcbgsEd67UaKGu4EZ0UlUDqOuiEC
[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-386
[dirmd] Roll dirmd to 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
mRL0OO6d95dgzOT7qyz6fT1FCUu-EyNu2NuSY-uqJNMC
[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 3d533070 Roll dirmd to git_revision:3d5330702211e01321af4fb53fec2f2f361137a7 to pick up https://chromium-review.googlesource.com/c/infra/infra/+/2597921 R=ehmaldonado@google.com Bug: 1154541 Change-Id: I0fd0b56a42b63fd3518396aca0d99dde9fd95547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2612385 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
5 years ago
git_revision:3d5330702211e01321af4fb53fec2f2f361137a7
qjuxYLAdUlWx_9GJ4xQLBe6ldevxsj8_C41_js__REIC
[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
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
-m2PUUpfbRxMfOwF0sHs1U4ZmtJ1uBfN2A9uxGhVqhQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-amd64
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
yODS32WeV82_sQvaywXjcNSB92IcECiA_u3BUIhBn3kC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-arm64
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
syvAlbbYzFC7-dUlIOUQ-B1wczrPtwaY4HU0VSunvKoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-armv6l
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
pZAm4TnZlfRAYeqlkPRb-UWx9LoQpPVsgLTew8qPhp8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-mips64
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
0fPKbUxR4KQ7U1SNGA0P3_2g0wUPNt0lpFj1GuGFj7QC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-mips64le
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
Oo77_B32HSGLLjKwZskyjMSRjVlPEcKzltErUs8sKKUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-mipsle
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
ov-l0q1ssZQJz8EmDJiUvg77vmFhMq5xWl4YhBT9oeIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-ppc64
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
N4WiYHHCRpRIRrjbg82MH6ffNf7qcQ12OMZB0b9WuBYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-ppc64le
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
NwsYOCdBtoBpEt0jA_LRHA6tx7SR8fhIIwJXUJrkps8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/linux-s390x
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
ENa1tYhCzDwaN-x9lbuPMTxi3x-gc6vsvCG7ewiBf9UC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/mac-amd64
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
zUWOs52o-5_C20dLSqZSa56ltNPcbPWqoGJ3CS9lNFEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
infra/tools/luci-auth/windows-386
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
qBSFBGah-oyPDnFOlqGVNN4cwAHt36fARBO26e6e7bcC
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci-auth/windows-amd64
[luci-auth] Update to the latest version. Has support for generating tokens through LUCI Token Server. Has somewhat nicer UX around `luci-auth context` usage. R=iannucci@chromium.org BUG=1082960 Change-Id: I2a77649b7ebbc5c99af4435afa929022a0e93ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2216533 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:510e7187aa80b1b0d490f069437d119c28d1ea48
albPp3qknhTtut8iNFavhAJ845aNVhILyJhY3UdivngC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-386
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
U0OeZBhdlOzNUvZKzkBpjEdKcgdzANafGuf-N3WebjkC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-amd64
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
ooOZpqCBAIKbrojk-VPOjwoXpKbCZcrl8ZXAdyy_wB4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-arm64
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
nu6vUd73I-0Ij4ckauUa6yxUYPV6aZyGfj8aM0T6ABUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-armv6l
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
-AuXn6_1OYma0YcAy0F3RTDC_HsUBnTuJcKCBhLDu7IC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mips64
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
pVIcLSRq8oaHn0gTZxtKa-VDDz53sYRgerj1gHEK7L4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mips64le
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
MDoqxATSuhLP18eO1ddGP8qVpOBYn-ygG0II7obUJWQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-mipsle
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
2Uu2igENPtzQXBRz1IlkPQzbId5tjdairUrMX2WoolMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-ppc64
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
4jJ-pBcnGdqXe-GXX6qphoaHa5rZ-pZcx3nCdK32diMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-ppc64le
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
ESzjIv0y0eAZhUqLQ9g_UFJd9JRC6SFBayvWg-5o8kMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/linux-s390x
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
OAtP4f6L2BpTY9M1fMoRJKQtWKUDUcY52i0ouwxxZSwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/mac-amd64
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
OyfbU6o7_zPV-ofksSZpbrLXOsd9ewyxlPzXD1Mv3HwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
infra/tools/luci/led/windows-386
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
wACUug-dmUsCf3et7fabZOlYfgt683zUEh9yGTjxssEC
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/led/windows-amd64
[depot_tools] Roll led to latest To release change: crrev.com/c/2490615 Bug: 1141272 Change-Id: I7b21f48881a42d98c1f4ea0883609f478e2d134e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2495573 Auto-Submit: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:657015d28a449e1846ef16269825886cc17e08ff
_qBzM_1xPe_PIPGQSzsJqqfjW7xi5zYj8jCxlk-gonIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-386
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
yqD-pIDjJ5mQghyApsYciD5jDhEvj67hbdMyQ-RbxNYC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-amd64
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
kluqX8UE7g3vOd9OR4z-usXPiC3rdgnYcA_kgFbw9yIC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-arm64
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
WjEXtw9Y4-uV7xzd2_piBMTQ3gENv1ltRcdc8yxXYdsC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-armv6l
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
WgApTU2DgEX9eF2NFalOLYA0dEVCt7a9hylumJLW2woC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
oMZEsnkk6DC8uRe7f7jpg9TBElDRbTNMlejQsG0jqTAC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mips64le
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
X8AUCuqlJiz5E1IZJttyHd51OiaTd3AwISKHNcCnx5UC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-mipsle
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
BcDa6_JxV_hCu9sksPjxy4kDG7MmGeKhJJRV40DOc-sC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
KerIzcb6v3DDSJ0cgpsRymI4CdboCye28Z1I6svF344C
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-ppc64le
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
MKF9wPjrvsvv98dPJ-V0cF9_4BglQQHcwGT3ag0O6wsC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/linux-s390x
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
WWE78UK4ta5fFHkaoX0pKxfAab0bVs0vIwii_JBL-LgC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/lucicfg/mac-amd64
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
OCUlrIVydnPeN6S7She4dpiyIGG64o-0VfGMpdtuLPYC
[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
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
infra/tools/luci/lucicfg/windows-386
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
KOTqOkWCMYh_AnsK823iHxDMCSQK6hAzz4MrmVlPLwQC
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 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/windows-amd64
[lucicfg] Update to 1.21.0. Adds `proto.has(msg, field)`. No other changes. R=iannucci@chromium.org BUG=1133442 Change-Id: I40a90aafa04059a57aac25bc56bb9505957c705b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2444090 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:71ad967b1f3b33b610a3d523706d43162f6a1907
MEsaq7RMs_7OLUvLQkmbePWL_j5ENMiYoGdfUL5lI5cC
[cipd] Add lucicfg tool. It knows how to interpret configuration files written in Starlark-based DSL and produce a bunch of protobuf messages as a result. Will be used to generate various infra configs. In particular, will be used by infra developers (to update configs), by PRESUBMIT.py on dev machines (to verify configs before uploading CLs) and by bots (to verify configs before submitting CLs). R=tandrii@chromium.org BUG=833946 Change-Id: Iceec7d808ce180f7d4a341fab8b5ce11933c2a6b Reviewed-on: https://chromium-review.googlesource.com/c/1444499 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-386
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
pNsHQp4WsQh9dLIt5b9MZWgEs3cgSDOhUJ8jw-Mo9TMC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-amd64
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
9n9aWmWzkCn2FCJg9837SwqH8_JibnMy9QozKNlhhR8C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-arm64
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
dHsCd9RhOjpUyLSlCw4RcyMNKNjHSAZzHlFVJKwNgDYC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-armv6l
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
J3jcmLaAwCSW-LCJclbKMqvQzwsfUlV1wvzuxlHLvLAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
TNiA-14rYihy8PE2fPQv0vIS5Ske49xbogWKIys9VdUC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mips64le
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
G4pGTyQZD9o_Kc7LCZZzRoFzSjJ93zCet3o0SElU2XIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-mipsle
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
LzPGHtnVXGUrjHfW4Xrw_iHFuVEBuF4YOb5Yd_LNePAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
6fG1dmjQ-V2SzMnspG1h7KpkNMDp22M4vNEGd64CZ5YC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-ppc64le
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
hz5bCGZ-xTKsY4w6cnjAeqEn4g11gpE6ZVoe9Qs4Z5wC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/linux-s390x
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
kUd5csUgKXx8XavSGxnv6XN3jHr_-I1nRkY_Lg1rbDsC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/mac-amd64
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
gMFqT_XlauWc5oPgxdOYbcuSJ5RRPkcYuRDxkjKGIbwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
infra/tools/luci/vpython/windows-386
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
fxi5UjJ-aPrRxRBcNbW7FhiSjpQJtJnCF3wKGZO7avcC
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/luci/vpython/windows-amd64
[cipd] Update cipd and vpython to latest versions. R=tandrii@chromium.org BUG=1124112 Change-Id: Ie303ebfc8d6b94645862d69fcd40fadbaf3d164a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2532900 Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:0f694cdc06ba054b9960aa1ae9766e45b53d02c1
qJhMxXrlHDCoQqWyi4PV9R09xKwTIxXux-arbuLgvrQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-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
Ping mac_toolchain to 6e584bf785867bc3b340f82bb2f7a6cd42ba22a8 To release change: https://crrev.com/c/2507431 Bug: 1143664 Change-Id: Idd8cefcd525d87bca98fb3c990558e3f95ca3930 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2510049 Reviewed-by: Jochen Eisinger <jochen@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
5 years ago
git_revision:6e584bf785867bc3b340f82bb2f7a6cd42ba22a8
wHJfq70TBoff204UUKBQmxSKrGa5hEpHFjd5IX5Q0EEC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-386
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
uljBrvEEopZNL4_cQXJhe1zwMJRuO34AZi4j-IRMeO4C
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-amd64
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
iV6F48NL7KbZv1P3skCEkqi1uSkw7_C6XtXRD-pVIYgC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-arm64
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
UDiuICqa_7AV1ug01OH-BtnLOTCLPRkxUap7c4_F-2IC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-armv6l
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
1mfP1cFhmVmyrH8EVtj_kRmuoupEA8XLOVIE58N43JIC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
eibJ8LnvqybmO2Bah7Vbgo-_UKJdvM1jBYIEo9dqK1oC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mips64le
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
GltwKuT_mgYn2t9RKzaUCjyPft-GPS4F61c-tkhfgUQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-mipsle
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
LIn2JHXmlgD8JlNQEvft9fiXpd4332CTNLY-3QlwnbwC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
zgS4PNs-qrVXr6sqSx6vluJfBugcEq6IAU7RNpuG9qoC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-ppc64le
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
0ltgT79UTpdCLznCJU60laegoRBobMTalPEr1quutbQC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/linux-s390x
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
0PFXoAorrEQtulgnLgfcPsTzlsBR09d3sJZn27x_XmkC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/mac-amd64
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
J8Vc2hyZPcFUOX67nSyl-1EOCn0t75LeN8e7jrGxxpAC
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
infra/tools/prpc/windows-386
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
K30BBGLyKE0c5Q62sM7Wc4tDjuRVTFEf_RY0vhRkewwC
Revert "cipd: remove windows-386" This reverts commit 314e30187959f6a98d1f1498690c8537711cf0af. Reason for revert: On second thought, I don't think we want this. Original change's description: > cipd: remove windows-386 > > Running depot_tools on Windows 32 bits is not supported anymore. > > Add a comment to cipd_manifest.txt to help people to figure out by themselves > where to look to do a roll. > > Change-Id: I8a8c2d1437ec77c99588261e3eba0abdcb13c105 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1630448 > Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=maruel@chromium.org,iannucci@chromium.org Change-Id: I206becbf5bde4bb12e9d71ccab13027171fb017f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1633030 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
6 years ago
[cipd] Pin hashes of CIPD packages. Together with already committed cipd_client_version.digests file, this cryptographically binds contents of CIPD packages used by depot_tools with depot_tool's git revision (assuming the CIPD client pinned by cipd_client_version.digests is trusted too, which can presumably be verified when it is being pinned). This holds true even if the CIPD backend is compromised. The worst that can happen is a denial of service (e.g. if the backend refuses to serve packages at all). If a bad backend tries to serve a malicious (unexpected) CIPD client, 'cipd' bootstrap script (and its powershell counterpart) will detect a mismatch between SHA256 of the fetched binary and what's specified in cipd_client_version.digests, and will refuse to run the untrusted binary. Similarly, if the bad backend tries to serve some other unexpected package (in place of a package specified in cipd_manifest.txt), the CIPD client (already verified and trusted as this point) will detect a mismatch between what was fetched and what's pinned in cipd_manifest.versions, and will refuse to install untrusted files. cipd_manifest.versions was generated from cipd_manifest.txt by: $ cipd ensure-file-resolve -ensure-file cipd_manifest.txt This will have to be rerun each time cipd_manifest.txt is updated. There's a presubmit check that verifies *.versions file is up-to-date (it's part of 'cipd ensure-file-verify'). BUG=870166 R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5 Reviewed-on: https://chromium-review.googlesource.com/1227435 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
7 years ago
infra/tools/prpc/windows-amd64
Roll prpc and rdb tools to the latest version R=vadimsh@chromium.org Change-Id: I8a0df0566e174e9d688daf8ba3ed4172c90a2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2220784 Auto-Submit: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
5 years ago
git_revision:dace3c38ddbc95ee87f77f6fac1d30b8333283e4
zniiDCa2RQN-VUlZl7UPRmipTkL4oRQTaJV8TGzuKKQC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
nIdmzpzCuZB_Mf7xBrTl2WLRK8vNRlXkh8tIeHjB1aAC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
FL53I_4LN9Gv1bIKmeyepEMqDVftdcUPIcIiDrTcitcC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
LgkslmPr8TsI5lAy-GFq3mQs6KR055p3XcsMn4vtVo4C
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
A9cnZZu44QtaLxX2byjP4ODYwRN37YxyxsD3h76XoO8C
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
AVu7-_xZrycHqHSYwmOE5leFgqnjmzo0k_NZpIgEkakC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
N80XcmiJmLmbYA9OTP9tYN3EEqLsD4PupEHkLA923rUC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
IoYsJ_KS0IA69-sdc3oW9x1tjeHsV2RGPNjVhmq0qnwC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
0naajoNRM8-zyUWIU2jZoL_IpoARLd-N3bj2WVdzo_oC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
vl8egt3r346QXGXqXfGugEeU5G_PjdXLcAaDq1x0G9kC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
Ag6qR9_MPxruQYsqmXeqt3uWxWfcpaL7P1qYjw4vPiMC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
N5R-y_GKBnIn57uLs5QsZOHgQTRIwx-xbhXlm5HEVYsC
[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-386
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
7zlgab0zXdd0fEDnzaYIGnFIWZqil_j1rvRJmNoG5vQC
[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
[resultdb] move cipd pin of infra/tools/rdb This is to deploy the change of https://crrev.com/c/2549432 to depot_tools. R=chanli@google.com,nodir@google.com CC=maruel@google.com,yuanzhi@google.com Bug: 1150844 Change-Id: I9aeb679009b0340536db0ad2063e3e8819271a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2550945 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Scott Lee <ddoman@chromium.org>
5 years ago
git_revision:0a941f5d4ab879de30e3fbd1f187505629aedb04
9LqyDycttydSSjvKCMiCC0yAXxSSNcsJpCmdfEBGrFAC