10-26-2016, 02:21 AM
Both Travis and CircleCI allow us to run CI tests. Currently CircleCI is used only for the stylecheck, while Travis does 4 builds for each commit. If we split the work better, we could have better CI roundtrip times. Say we move the gcc builds over to CircleCI, and let only the Travis' clang builds check the LuaAPI documentation status, then both CIs will run more or less the same amount of time. On the other hand, we would lose the ability to detect style issues very early, the entire CircleCI build will need to finish before the style violations would get reported back to Github. Would it still be worth the change?
To sum up, these are the checks currently done on Linux:
- BasicStyleCheck
- Build gcc and clang, debug and release
- Check LuaAPI documentation status (must build before checking)
Alternatively, perhaps there's yet another CI provider where we could offload some of the checks?
To sum up, these are the checks currently done on Linux:
- BasicStyleCheck
- Build gcc and clang, debug and release
- Check LuaAPI documentation status (must build before checking)
Alternatively, perhaps there's yet another CI provider where we could offload some of the checks?