remove outdated info

.gitattributes

@@ -3,6 +3,4 @@
 
 .gitattributes export-ignore
 .gitignore export-ignore
-.travis.yml export-ignore
-appveyor.yml export-ignore
 *.sh		eol=lf

Makefile

@@ -46,7 +46,7 @@ endif
 
 ADD_REVISION?=0
 
-BRANCH=$(shell echo $$APPVEYOR_REPO_NAME | grep -q /haxe && echo $$APPVEYOR_REPO_BRANCH || echo $$TRAVIS_REPO_SLUG | grep -q /haxe && echo $$TRAVIS_BRANCH || git rev-parse --abbrev-ref HEAD)
+BRANCH=$(shell git rev-parse --abbrev-ref HEAD)
 COMMIT_SHA=$(shell git rev-parse --short HEAD)
 COMMIT_DATE=$(shell \
 	if [ "$$(uname)" = "Darwin" ]; then \

libs/README.md

@@ -1,5 +0,0 @@
-# ocamllibs
-
-[![TravisCI Build Status](https://travis-ci.org/HaxeFoundation/ocamllibs.svg?branch=master)](https://travis-ci.org/HaxeFoundation/ocamllibs)
-
-Various OCaml libraries.

tests/README.md

@@ -2,42 +2,7 @@
 
 We have a number of test suites, which are placed in their own folders in this directory.
 
-"RunCi.hx" is the script used by our CIs to run all the test suites. It is possible to configure CIs for your own fork of Haxe on Github using the instructions as follows.
-
-### TravisCI
-
-TravisCI provides Linux and Mac builds. However, for forks, it only provides Linux builds unless [requested manually](http://docs.travis-ci.com/user/multi-os/).
-
-To set up TravisCI:
-
- 1. Head to TravisCI, go to the [profile page](https://travis-ci.org/profile).
- 2. Turn on the switch of your fork. If you couldn't find the repo, try the *Sync* button on the top to refresh the list.
- 3. If you want to enable browser testing for the JS target, follow the instructions in the SauceLabs section. If not, go to the next step.
- 4. Push to the repo to trigger a new build. The build result should be available at `https://travis-ci.org/<user_name>/haxe`.
-
-### AppVeyor
-
-AppVeyor provides Windows builds.
-
-To set up AppVeyor:
-
- 1. Head to AppVeyor, [add a new project](https://ci.appveyor.com/projects/new).
- 2. Select the forked repo under your account.
- 3. Push to the repo to trigger a new build. The build result should be available at `https://ci.appveyor.com/project/<user_name>/haxe`.
-
-### SauceLabs
-
-SauceLabs provides browser testings. We use TravisCI to drive the test, so you should have TravisCI configured.
-
-To set up SauceLabs:
-
- 1. Head to the project page of your fork at `https://travis-ci.org/<user_name>/haxe`
- 2. Select *Settings* -> *Settings*.
- 3. Select the *Environment Variables* tab.
- 4. Select *Add a new variable* for the following pairs, keeping the switch off for *Display value in build logs*.
-    * name: `SAUCE_USERNAME`, value: your SauceLabs account name
-    * name: `SAUCE_ACCESS_KEY`, value: your SauceLabs access key, which can be found at https://saucelabs.com/account
- 5. Push to the repo to trigger a new TravisCI build. SauceLabs test results should be available in the JS build log.
+"RunCi.hx" is the script used by our CIs to run all the test suites.
 
 ### Local testing