tree: 5b7e4029eebbb87edace4e81bbe1f176112dbdf8 [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. sshwatcher/
  28. syz-repro-automation/
  29. syzbot-autotriager/
  30. tast-ab-test/
  31. variant/
  32. arm_trusted_firmware_uprev
  33. cargo2ebuild.py
  34. cleanup_crates.py
  35. common.sh
  36. cros_check_firmware_tarball
  37. cros_update_firmware
  38. device_summary.sh
  39. dut-console
  40. feedback-unpack
  41. findfix.py
  42. forward_usb_devices.py
  43. fromupstream.py
  44. gbatch
  45. gen_uprev_msg.py
  46. get_binhost.py
  47. get_local_manifest
  48. git-clean-refs
  49. github-fetch-archives
  50. graphviz_overlays.py
  51. kernel_decode_stack
  52. merge-kernel
  53. mod_recovery_for_decryption.sh
  54. OWNERS
  55. power_qual_compare.py
  56. README.md
  57. repo-patch
  58. search_blocked_words.sh
  59. servoinfo
  60. setup_cros_cargo_home
  61. shflags
  62. update_aosp.sh
  63. update_gpu_drivers.sh
  64. update_program_fw
  65. uprev_firmware.sh
  66. uprev_scp_firmware.sh
  67. upstream_diff.py
  68. 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.