Automatic Boards Manager release for builds triggered by the creation of a git tag

Travis CI defines the TRAVIS_TAG environment variable when the build is triggered by the creation of a tag.

Check if TRAVIS_TAG is defined.
Create installation archive file
1. Delete .gitignore and any other unnecessary Git files if present
2. Move files up from the architecture subfolder
3. Compress
4. Calculate checksum
Update the JSON file
Do a test Boards Manager installation and compile with the installed boards with the specified IDE range.
Commit the installation archive and JSON file to the release repository

IDE range for testing the Boards Manager installation
Sketch or sketch folder to use for testing
Github personal access token for committing to the Boards Manager release repository
Package source folder: location of the hardware package files in the repository. Some are located in a subfolder of the repository.
Release information
- Boards Manager release repository
- Boards Manager release branch
- Boards Manager release folder
JSON file configuration information:
- platform information
- name
- architecture
- onlineHelp
- boards
- toolsdependencies (must be able to handle multiple tools, should this be a separate function that can be called multiple times?):
  - packager
  - name
  - version

The repository has the 1.5 hardware package structure (architecture folder).
The JSON file already has the package information and all necessary tools entries
New tools entries will be added to the JSON file manually when necessary
- It seems just as easy for the JSON file to be edited as the .travis.yml file

I don't believe any of these are run automatically

per1234 / arduino-ci-script