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