Continuous integration software (Jenkins, Hudson, Travis, etc)

[hab136]

Does anyone use any continuous integration setups with KSP development?

Github just bugged me about plugging in CI software and I was like.. "huh, I bet that would work".

[sarbian]

Yeah, the main benefits is automated unit testing but doing that with a KSP mod is a bit complex (if doable at all). The other one is ease of distribution and compiling, that that's what I do

[djungelorm]

I use Travis to run the unit tests for the kRPC mod (an RPC server with clients in various languages). If you just have a C# project and some NUnit tests, it is actually pretty straightforward to get travis set up and running. The only issue is making the DLLs from KSP_Data/Managed available to Travis. I do it by having it download an encrypted archive from AWS (encrypted so that I'm not distributing copyright material...) containing the DLLs. You can then put the encryption key as an environment variable in the Travis settings, where it's hidden from all but the project owner (as long as you're careful not to echo it in the log files!)

Obviously, running any integration tests on a CI server that require KSP to be running is out of the question. Instead, I have a bunch of python scripts to test the mod with KSP running on my local machine: https://github.com/krpc/krpc/tree/master/service/SpaceCenter/test Very useful to spot when Squad change the APIs!