Add configuration for CI: Travis-CI and AppVeyor

[awwad]

The addition of these simple .travis.yml and appveyor.yml files here configures Travis-CI and AppVeyor to run automated tests for each push to the repository.

An explanation of CI setup and configuration is currently available here.

[awwad]

You can see the build results here: https://travis-ci.org/SeattleTestbed/seattlelib_v2
This includes a variety of failures, listed here as links to the build output with the relevant lines highlighted:

• Running: ut_seattlelib_dylinkrepyportabilityimportmodulesymbols.py [ FAIL ]
• Running: ut_seattlelib_httpretrieve_content.py [ FAIL ]
• (excluding the other errors in that class of "'dy_import_module_symbols' is not defined")
• Running: ut_librepy_recvmess-reuse.r2py [ FAIL ]
• Running: ut_librepy_socket-nonblocksend.r2py [ FAIL ]
• Running: ut_librepy_waitforconn-reuse.r2py [ FAIL ]
• Running: ut_librepy_waitforconn-stop.r2py [ FAIL ]

[awwad]

I won't go into the same amount of detail for all the other Travis-CI runs, or the AppVeyor runs here, but most of them are similar.

[awwad]

Seems to be working as intended now - 3 Python versions on Linux (2.5, 2.6, 2.7), 2 on OS X (2.6, 2.7), and 2 on Windows 2012 Server RC2 (2.6, 2.7), with the Windows builds running on 32- and 64-bit architecture.

[lukpueh]

I confirm successful runs using provided travis-CI config on seattlelib_v2 master branch and test branch by pushing newly created .travis.yml to each branch respectively. Tests ran on Linux (Python v2.7.9, v2.6.9, v2.5.6) and OS X (v2.7.5, v2.6.9). Here are the branch build results.

[lukpueh]

.travis.yml and .appvoyer.yml are generic for all(?) SeattleTestbed components so it would be nice to have a central SeattleTestbed/CI repo for the config files where they can be maintained and cloned from.

[awwad]

That (central config) is a good point, Lukas. (: Maybe they can live in SeattleTestbed/common or SeattleTestbed/buildscripts. Thoughts?

[lukpueh]

SeattleTestbed/buildscripts sounds good. SeattleTestbed/common rather not since these files are fetched during building (catch-22?).

[lukpueh]

Candidates and docs for this PR have moved (see SeattleTestbed/continuous-integration#2 and SeattleTestbed/docs#19). We'll address modifications there and also deploy the fresh CI configs from there. I'm closing this PR for the time being.

To be sure that we won't omit any changes, I locally compared the relevant files:

$ diff -u continuous-integration/appveyor.yml seattlelib_v2-awwad/appveyor.yml
# no output - files don't differ
$ diff -u continuous-integration/.travis.yml seattlelib_v2-awwad/.travis.yml
# no output - files don't differ