Like the ci-monkey that goes around finding repos to give ci builds to automatically, the upgrade-monkey goes around finding infrastructure to upgrade.
- different "modules" for each upgradeable piece
- jenkins "module" goes to find if there are updates for jenkins and does them
- module could be file or function or separate repo
- current version is stored in config file passed to binary with -c flag
- alert
- Denote version locks (Major/Minor/Patch? Minor first Patch (1.1.1 instead of 1.1.0)
- I don't know go, using this to learn
- Folder structure is because of this: https://golang.org/doc/code.html, specifically the "Your first program" section
export PATH=$PATH:/usr/local/go/bin
export PATH=$PATH:~/git/upgrade-monkey/bin
export GOPATH=~/git/upgrade-monkey
vi src/github.com/wsoula/upgrade-monkey/upgrade-monkey.go
go install github.com/wsoula/upgrade-monkey
bin/upgrade-monkey