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