Skip to content

C
Chromium_Depot_tools
Switch branch/tag
  1. 13 Mar, 2019 1 commit
    • Vadim Shtayura's avatar
      [lucicfg] Bump lucicfg version 1.5.3 -> v1.5.4. · deb384f9
      Vadim Shtayura authored 
      Changes:
2019-03-12 seanabraham@chromium.org chromiumos-protos: Use new builder proto location
2019-03-12 vadimsh@chromium.org [lucicfg] Implement 'equivalent_to' support in CQ config generator.
2019-03-12 dburger@chromium.org Add Id and General configs to BuilderConfig.
2019-03-12 seanabraham@chromium.org testplans: Use protos in chromiumos/infra/proto rather than in lucicfg/external
2019-03-12 hinoka@google.com [milo] Add default_commit_limit and default_expand to console definitions
2019-03-11 vadimsh@chromium.org [lucicfg] Recognize e.g. 'builder = lucicfg.rule(impl = _builder)' in docgen.

R=tandrii@chromium.org, nodir@chromium.org
CC=dburger@chromium.org

Change-Id: I73a54bfe19a86e59e22bd320df6b4d414f654a7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1521149Reviewed-by: 's avatarNodir Turakulov <nodir@chromium.org>
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
      deb384f9
  3. 07 Mar, 2019 1 commit
    • Vadim Shtayura's avatar
      [lucicfg] Bump lucicfg version 1.3.2 -> 1.5.3. · b139178f
      Vadim Shtayura authored 
      Changes:
2019-03-07 dburger@chromium.org Add dummy BuilderConfig proto to lucicfg external protos.
2019-03-06 vadimsh@chromium.org [lucicfg] Forbid "luci.*" bucket names in luci.bucket(...).
2019-03-06 vadimsh@chromium.org [lucicfg] Use 'flatten_buildbucket_cfg' tool to normalize cr-buildbucket.cfg.
2019-03-06 vadimsh@chromium.org [lucicfg] Add 'triggered_by' support to CQ config generator.
2019-03-06 vadimsh@chromium.org [lucicfg] Add "lucicfg semantic-diff" subcommand to aid in the migration.
2019-03-05 vadimsh@chromium.org [lucicfg] Add luci.cq_tryjob_verifier(...).
2019-03-05 vadimsh@chromium.org [lucicfg] Add retry_config support.
2019-03-04 vadimsh@chromium.org [lucicfg] Initial implementation of luci.cq_group(...).
2019-03-02 vadimsh@chromium.org [lucicfg] Make '#!/usr/bin/env lucicfg' work.
2019-02-28 vadimsh@chromium.org [lucicfg] Add luci.cq(...) rule.
2019-02-27 vadimsh@chromium.org [lucicfg] Get rid of `refs_regexps`, always accept regexps via `refs`.
2019-02-27 seanabraham@chromium.org crostesting: Change "BuildCritera" to "TargetCriteria"

R=tandrii@chromium.org

Change-Id: I8477088c50764ba847424eb1e59be34d03d86eb1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1509016
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: 's avatarAndrii Shyshkalov <tandrii@chromium.org>
      b139178f
  5. 28 Feb, 2019 1 commit
  7. 26 Feb, 2019 1 commit
  9. 22 Feb, 2019 1 commit
  11. 20 Feb, 2019 1 commit
    • Robert Iannucci's avatar
      [led] Update to latest version · 7d7746ca
      Robert Iannucci authored 
      cc015d890 Roll infra/go/src/go.chromium.org/luci/ 0d6874412..340fb1e12 (7 commits)
2378074b7 [led] Give auth-login advice everywhere we get an authClient.
b48969046 Roll infra/go/src/go.chromium.org/luci/ e48c958d0..44257920e (6 commits)
072630eb2 [led] Edit the right properties instead of the old properties :)
1673f6db0 [led] Remove interface abstraction
44ab51ec6 [led] Remove support for rietveld URLs.

R=nodir@chromium.org

Change-Id: Ic4d4842722a63bbd2369feff8c7df722eab86865
Reviewed-on: https://chromium-review.googlesource.com/c/1474426
Auto-Submit: Robbie Iannucci <iannucci@chromium.org>
Reviewed-by: 's avatarNodir Turakulov <nodir@chromium.org>
Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
      7d7746ca
  13. 12 Feb, 2019 1 commit
  15. 05 Feb, 2019 1 commit
  17. 30 Jan, 2019 1 commit
    • Vadim Shtayura's avatar
      [cipd] Add lucicfg tool. · ef40cbac
      Vadim Shtayura authored 
      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: 's avatarAndrii Shyshkalov <tandrii@chromium.org>
      ef40cbac
  19. 13 Dec, 2018 1 commit
  21. 21 Nov, 2018 1 commit
  23. 20 Nov, 2018 2 commits
  25. 16 Nov, 2018 1 commit
  27. 15 Nov, 2018 1 commit
  29. 12 Nov, 2018 1 commit
  31. 10 Nov, 2018 1 commit
  33. 09 Nov, 2018 1 commit
  35. 09 Oct, 2018 1 commit
  37. 05 Oct, 2018 1 commit
  39. 03 Oct, 2018 1 commit
  41. 24 Sep, 2018 1 commit
  43. 18 Sep, 2018 1 commit
    • Vadim Shtayura's avatar
      [cipd] Pin hashes of CIPD packages. · 01710d04
      Vadim Shtayura authored 
      Together with already committed cipd_client_version.digests file, this
cryptographically binds contents of CIPD packages used by depot_tools
with depot_tool's git revision (assuming the CIPD client pinned by
cipd_client_version.digests is trusted too, which can presumably be
verified when it is being pinned).

This holds true even if the CIPD backend is compromised. The worst that
can happen is a denial of service (e.g. if the backend refuses to serve
packages at all).

If a bad backend tries to serve a malicious (unexpected) CIPD client,
'cipd' bootstrap script (and its powershell counterpart) will detect
a mismatch between SHA256 of the fetched binary and what's specified in
cipd_client_version.digests, and will refuse to run the untrusted binary.

Similarly, if the bad backend tries to serve some other unexpected
package (in place of a package specified in cipd_manifest.txt), the CIPD
client (already verified and trusted as this point) will detect a mismatch
between what was fetched and what's pinned in cipd_manifest.versions, and
will refuse to install untrusted files.

cipd_manifest.versions was generated from cipd_manifest.txt by:
$ cipd ensure-file-resolve -ensure-file cipd_manifest.txt

This will have to be rerun each time cipd_manifest.txt is updated. There's
a presubmit check that verifies *.versions file is up-to-date (it's part
of 'cipd ensure-file-verify').

BUG=870166
R=nodir@chromium.org, iannucci@chromium.org, tandrii@chromium.org

Change-Id: I25314adf0a9b05c69cd16e75aff01dbc79c87aa5
Reviewed-on: https://chromium-review.googlesource.com/1227435
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: 's avatarAndrii Shyshkalov <tandrii@chromium.org>
      01710d04