Building a Haxe Project
What This Guide Covers
Travis CI support for Haxe is contributed by the community and may be removed or altered at any time. If you run into any problems, please report them in the Travis CI issue tracker and cc @andyli @waneck @Simn.
Choosing Haxe versions to test against
Haxe workers on travis-ci.org download and install the binary of Haxe.
To select one or more versions, use the
key in your
.travis.yml file, for example:
language: haxe haxe: - "3.2.1" - stable # the latest stable release defined in https://haxe.org/download/list/ - development # the latest build of the development branch in http://build.haxe.org/
Default Haxe Version
If you leave the
haxe: key out of your
.travis.yml, Travis CI will use
stable, which is
the latest stable release defined in the haxe.org download list.
Default Neko Version
By default, Neko 2.2.0 will also be downloaded and installed.
neko: key in your
.travis.yml file to specify a different Neko version,
language: haxe neko: "2.0.0"
haxe:, you can provide only one value (not an array) to
If your project makes use of the standard hxml files for building, you can specify
the list of hxml files using the
hxml: key, for example:
language: haxe hxml: - build.hxml
In the install phase, the worker will run
yes | haxelib install $hxml for
each of the provided values. Similarly, in the script (test) phase,
the worker will run
haxe $hxml for each of the provided values.
You can replace the default install and script behavior by using the
script: keys, respectively, as described
in the general build configuration guide.
For Haxe projects,
haxe: can be given as arrays
to construct a build matrix.
The versions of Haxe and Neko a job is using are available as: