833e23f9e6
So far compilers needed to be specified twice (as usual with Travis in "compiler" as well as in our own CMPLR environment variable). This change allows our scripts to use the compiler specified with Travis (no need to populate CMPLR anymore).
Continuous Integration Scripts for EPICS Modules
The scripts in this repository are intended to provide a common, easy-to-use and flexible way to add Continuous Integration to EPICS software modules, e.g. Device Support modules.
By including this repository as a Git Submodule, your module will always use an explicit commit, i.e. a fixed version of the scripts. That way, further development of these scripts cannot break your setup.
Travis-CI
Features
- Compile against different version of EPICS Base
- Use different versions of compilers (gcc, clang)
- Cross-compile for Windows 32bit using MinGW and WINE
- Cross-compile for RTEMS 4.9 and 4.10
- Compile on MacOS
How to Use these Scripts
-
In your Support Module, add this respository as a Git Submodule (name suggestion:
.ci).$ git submodule add https://github.com/epics-base/ci-scripts .ci -
Create a Travis configuration by copying one of the examples.
$ cp .ci/.travis.yml.example-full .travis.yml -
Edit the
.travis.ymlconfiguration to include the jobs you want Travis to run. -
Push your changes and check travis-ci.org for your build results.