Closed awwad closed 8 years ago
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.
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 seash-awwad/appveyor.yml
# no output - files don't differ
$ diff -u continuous-integration/.travis.yml seash-awwad/.travis.yml
--- continuous-integration/.travis.yml 2016-08-18 17:43:08.000000000 -0400
+++ seash-awwad/.travis.yml 2016-08-18 17:46:16.000000000 -0400
@@ -65,7 +65,7 @@
# recipe.
- language: generic
os: osx
- env: Python='2.6.9' PythonBin="/Users/travis/.pyenv/versions/2.6.9/bin/python"
+ env: Python='2.6.9' PythonBin="/Users/travis/.pyenv/versions/2.6.9/bin/python" TERM='linux'
install:
#brew update;
#brew install python26; # This is no longer available.
@@ -82,5 +82,6 @@
- $PythonBin initialize.py;
- $PythonBin build.py -t;
- cd ../RUNNABLE;
+ - echo $TERM;
- $PythonBin utf.py -a;
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 SeattleTestbed/seash repository.
An explanation of CI setup and configuration is currently available here.
In this particular case, because I don't have admin access to SeattleTestbed/seash (I would guess that's due to a quirk in the group permissioning.), I can't do the Travis-CI-side or AppVeyor-side configuration (which is easy).
When that's done, builds will be visible here: