Dear all,
I just released a new major version of the ci-scripts module.
Here's the pitch:
This is a pretty easy way to get a pretty sophisticated Travis-CI setup.
If you own an EPICS module (Device Support etc.) hosted on GitHub...
And you would you like it to be automatically compiled (and tested) using different versions of Base, different compilers etc....
Adding ci-scripts as a git submodule gets you started with tested Travis-CI configurations for a lot of compilers (including MacOS and cross-compilation to Windows and RTEMS) and a mechanism to specify your module's dependencies (like Base, ASYN or the Sequencer) as releases or branches.
The ci-scripts are developed, shared, tested and released under the umbrella of the epics-base organization on GitHub. As a git submodule, you are always using a specific version that will not change "under your feet". You update your ci-scripts whenever you want and when it fits your software's life cycle.
It's even, well... documented.
Thanks a lot to Michael Davidsaver, Dirk Zimoch and Martin Konrad for their work and beta testing.
Please give it a try and contribute if you have more ideas.
Cheers,
~Ralph
ps. next planned major step: native Windows builds on AppVeyor.
