Tardis & Continuous Integration

[Nick May]

Has anyone looked at setting up a CI job for Tardis?

• Which CI server do you use? (Jenkins, Travis-CI, etc.)
  
• How do you provision VMs?
• Is Tardis installed with Chef, Salt, or other method?
• What tests are run?
  

This would provide some warning when package updates break the installation process, and let us check the build on multiple versions of operating systems.

[Grischa Meyer]

Travis-CI is being run for every commit to the main code base. However, it does not test regularly whether any package updates break the installation. (CI must be short for commit-integration ...)

It would be great if we had that though, I agree.

If I remember correctly, RMIT has a Hudson server running already? Maybe ask Ian about it? It might not be too hard to set up a mytardis installation on that server. The Travis configuration file has all the build steps described in it.

For the salt states there are no tests at the moment. I am completely rewriting my version anyway and I believe yours would have diverged a fair bit also.

--
You received this message because you are subscribed to the Google Groups "tardis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tardis-devel...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.