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