tree: 5b8f872285add25572e5d7198da7079914abdd5e [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_openwrt_sources/
  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. lium/
  24. net-auditor-parser/
  25. power_measurement/
  26. QPOP/
  27. refactor/
  28. refactor-libchrome/
  29. release/
  30. roafteriniter/
  31. sdtteam/
  32. snag/
  33. sshwatcher/
  34. syz-repro-automation/
  35. syzbot-autotriager/
  36. tast-ab-test/
  37. triage/
  38. variant/
  39. arm_trusted_firmware_uprev
  40. cargo2ebuild.py
  41. cleanup_crates.py
  42. common.sh
  43. coredropmerger.py
  44. cros_check_firmware_tarball
  45. cros_update_firmware
  46. device_summary.sh
  47. dtb_compare.py
  48. dut-console
  49. enable_rootfs_verification.sh
  50. feedback-unpack
  51. findfix.py
  52. flash_ssh_image
  53. forward_usb_devices.py
  54. fromupstream.py
  55. gbatch
  56. gen_uprev_msg.py
  57. get_binhost.py
  58. get_local_manifest
  59. git-clean-refs
  60. github-fetch-archives
  61. graphviz_overlays.py
  62. gscp.py
  63. kernel_decode_stack
  64. merge-kernel
  65. mod_recovery_for_decryption.sh
  66. OWNERS
  67. pasit_tast_satlab_setup.sh
  68. power_qual_compare.py
  69. README.md
  70. repo-patch
  71. search_blocked_words.sh
  72. servoinfo
  73. setup_cros_cargo_home
  74. shflags
  75. update_aosp.sh
  76. update_gpu_drivers.sh
  77. update_program_fw
  78. uprev_firmware.sh
  79. uprev_scp_firmware.sh
  80. upstream_diff.py
  81. 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.