Get our vision code packaged onto a Pi about trackerboxreloaded

[ounsworth]

Question: how to make it idiot-proof to pull updates from github to the robot's pi to avoid oopsies in the pit at competition?

• We want to avoid "oops, I checked in the Windows version" or "oops, I forgot to rebuild it after pulling"
• Idea1: make sure the build.gradle file that's on master is set to build for raspbian, and add build.gradle to the gitignore so nobody accidentally checks it in with Windows turned on.
• Idea2: check in some scripts that make it easier to work on the pi:
  • start.sh -- launch the vision process, will not persist across reboots. Include in here calling the utility to set contrast / brightness / autowhitebalance off for the Microsoft Lifecam.
  • stop.sh -- kills the vision process, whether started by start.sh or started at boot.
  • install.sh -- inserts the vision process into the system boot scripts.
  • uninstall.sh -- removes the vision process from the system boot scripts
  • update.sh -- stop.sh; git pull; gradlew build; start.sh
• Idea3 (Ken):
  • stop.sh, start.sh, install.sh, uninstall.sh same as above. update.sh designed to run on a laptop, scp the jar over, and restart the process. Copy the old jar to *jar.bkup
• Idea4 (Kevin): split update.sh into two separate parts: pullFromGit.sh and pushToPi.sh, where the push script does not require the laptop to have internet.

PS do some learning about systemd / sysvinit to do the start on boot stuff.