tree: ecf96327fd588dbe29887d4edf58c720d5f4a632 [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_openwrt/
  10. cros_ubuntu/
  11. cros_wifi_noise_calibration/
  12. cvetriager/
  13. emacs/
  14. fflash/
  15. findmissing/
  16. firmware/
  17. forklift/
  18. gfx/
  19. kernel-rebase/
  20. labtunnel/
  21. lium/
  22. net-auditor-parser/
  23. power_measurement/
  24. refactor/
  25. refactor-libchrome/
  26. roafteriniter/
  27. snag/
  28. sshwatcher/
  29. syz-repro-automation/
  30. syzbot-autotriager/
  31. tast-ab-test/
  32. variant/
  33. arm_trusted_firmware_uprev
  34. cargo2ebuild.py
  35. cleanup_crates.py
  36. common.sh
  37. cros_check_firmware_tarball
  38. cros_update_firmware
  39. device_summary.sh
  40. dut-console
  41. feedback-unpack
  42. findfix.py
  43. forward_usb_devices.py
  44. fromupstream.py
  45. gbatch
  46. gen_uprev_msg.py
  47. get_binhost.py
  48. get_local_manifest
  49. git-clean-refs
  50. github-fetch-archives
  51. graphviz_overlays.py
  52. kernel_decode_stack
  53. merge-kernel
  54. mod_recovery_for_decryption.sh
  55. OWNERS
  56. power_qual_compare.py
  57. README.md
  58. repo-patch
  59. search_blocked_words.sh
  60. servoinfo
  61. setup_cros_cargo_home
  62. shflags
  63. update_aosp.sh
  64. update_gpu_drivers.sh
  65. update_program_fw
  66. uprev_firmware.sh
  67. uprev_scp_firmware.sh
  68. upstream_diff.py
  69. 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.