Great work red-kangaroo. Before I can make a windows build, can you
1. Go through all the .sh files and change their permissions back to 755.
For example, in the diff on GitHub we have:
.devsPrefs/prepareUser.sh 100755 → 100644
Means the file permissions for this shell file have changed from 755 to 644.
Follow this link to see exactly how to do it: http://linuxcommand.org/lc3_lts0090.php
After that just commit to your branch and push. I can't remember if there are any special git steps for changing file permissions.
2. Compile the code with wizard mode deactivated. Do this by omitting the
. Then fix the compile errors you see there.
After these two steps you will see Travis light up green for all the build configs. In the first case, the release configs rely on being able to execute
certain shell scripts for packaging purposes. When the file permissions change to read only, then the containers cannot execute the commands written in the scripts because that user (Travis?) no longer has permission to do anything other than read the file.
In the second case this is just a regular compile error
I ran into these problems once before, ages ago when I first started messing with this CI business. I found the chmod thing to be quite handy Linux knowledge.
Also, you should be able to build your own windows build on your personal fork by creating, for example, a release branch, and building "manually" on Travis (i.e. log on and press the button)
or even changing the yaml file to tickle up your own containers on Travis. That's how I drafted the build system without working on the live repository
Any build artifacts will just appear in the red-kangaroo/ivan releases page.