Add travis testing to Irssi scripts.

[ailin-nemui]

This is start of issue #9

[ahf]

Overall, I think this is good. I do however want the .zsh files to be converted to either bash or posix sh. It should be possible for other people to run these checks locally without having to install a new shell.

The sample reports looks really cool. Very good job.

[ailin-nemui]

I think this should be good now. To enable commit rights, you need to create an App Token on an account with access to the repo, then run "travis encrypt REPO_LOGIN_TOKEN=yourtokenhere --add" inside the check-out and commit the key

[ahf]

Very nice, thanks! Let's see how this go.

[GeertHauwaerts]

I see a big amount of scripts in the whitelist, what exactly needs to be changed in those scripts in order to make them compliant?

[ailin-nemui]

@GeertHauwaerts the (very arbitrary) rules we set for now are: compiles, loads, uses strict all the way through, and has %IRSSI & $VERSION. See https://github.com/irssi/scripts.irssi.org/tree/gh-pages/_testing#irssi-scripts-testing.

Once you enable the commit rights for travis, it will generate a HTML report including links to the extracted log files for easier fixing of scripts. Until then, you can look at the raw results table visible in the build log at https://travis-ci.org/irssi/scripts.irssi.org which should show up if it was properly enabled (but which is not as complete)

Click on the triangle next to $ ./_testing/travis/show-failures.zsh (at the very end) to see the log messages of scripts that failed to load/compile.

The others will be failures due to missing $VERSION ("HDR") or strictures ("CRIT")