Google Git
Sign in
chromium / chromiumos / platform / dev-util / refs/heads/stabilize-15926.B / . / contrib
tree: 3c907771ad13b247edb3752137fe936fd58228f8 [path history] [tgz]
  1. branch_tools/
  2. btpeer_manager/
  3. chameleon/
  4. chromium_metadata/
  5. coil_urls/
  6. contrib/
  7. copybot/
  8. corp-ssh-helper-helper/
  9. cros_ca/
  10. cros_ca_linux/
  11. cros_openwrt/
  12. cros_ubuntu/
  13. cros_wifi_noise_calibration/
  14. cvetriager/
  15. dump-macro/
  16. emacs/
  17. fflash/
  18. findmissing/
  19. firmware/
  20. forklift/
  21. gfx/
  22. kernel-rebase/
  23. labtunnel/
  24. lium/
  25. net-auditor-parser/
  26. power_measurement/
  27. QPOP/
  28. refactor/
  29. refactor-libchrome/
  30. roafteriniter/
  31. snag/
  32. sshwatcher/
  33. syz-repro-automation/
  34. syzbot-autotriager/
  35. tast-ab-test/
  36. variant/
  37. arm_trusted_firmware_uprev
  38. cargo2ebuild.py
  39. cleanup_crates.py
  40. common.sh
  41. cros_check_firmware_tarball
  42. cros_update_firmware
  43. device_summary.sh
  44. dut-console
  45. enable_rootfs_verification.sh
  46. feedback-unpack
  47. findfix.py
  48. forward_usb_devices.py
  49. fromupstream.py
  50. gbatch
  51. gen_uprev_msg.py
  52. get_binhost.py
  53. get_local_manifest
  54. git-clean-refs
  55. github-fetch-archives
  56. graphviz_overlays.py
  57. gscp.py
  58. kernel_decode_stack
  59. merge-kernel
  60. mod_recovery_for_decryption.sh
  61. OWNERS
  62. power_qual_compare.py
  63. README.md
  64. repo-patch
  65. search_blocked_words.sh
  66. servoinfo
  67. setup_cros_cargo_home
  68. shflags
  69. update_aosp.sh
  70. update_gpu_drivers.sh
  71. update_program_fw
  72. uprev_firmware.sh
  73. uprev_scp_firmware.sh
  74. upstream_diff.py
  75. willis.go
contrib/README.md

Unsupported Chrome OS dev scripts

This directory is a place that developers can put scripts that are useful to them and that might be useful to other developers.

A few notes about what's here:

  • Nothing here may be used by build scripts. It's expected to only contain scripts that are run manually.
  • Nobody in the build team maintains these files. If something is broken, you can try using the git history to find someone to help you, but even better you should upload a fix yourself.
  • Chrome OS infrastructure makes no promises to keep scripts in here working. AKA: if you rely on some tool in “chromite”, or on some Google server, or something else official. ...and if that thing changes in a way that breaks you. ...then it's up to you to change your script. The change that broke you will not be reverted.

That being said: enjoy.