While unsuccessfully trying to add to the current deployment script, I realised that the complete deployment process should be cleaned-up and properly documented.

Currently, Travis executed config/deploy_to_github_pahes-sh upon success. This script clones MyWarp/mywarp.github.io, copies the matching build artefacts, writes a YML file with the build information (version, git-revision, git-tag, build-date, artefact names) and pushed the changes to the upstream repo. This toggles a build of the website.

Several points can be improved:

• call the script using Travis' deploy.provider.script option and remove the then unneeded if statement
• simplify declaration of binaries to store and eliminate extglob, possible use a simple include/exclude pattern
• have Gradle create a version.properties upon build the includes all required version information and have the script read from there instead of using various environment variables
• Use yq to write the YML file (or switch to JSON using jq)
• modularise the script (if it makes sense)
• document what is going on using inline comments, messages and possibly a readme in the config folder

Alternatively, investigate whether we can use Gradle directly and get rid of the shell script altogether.

See here for an example.