> Would you like to make that jenkins setup on jenkins.buildacloud.org? Sure I can add it on if you wish. Some of it would be a repeat of what you guys already have. I assume there's some sort of rules about building non-oss binaries on the public jenkins too?
> I'm sure it would benefit others to run the checkin tests > automatically. What would you need to get going on that? The checkin tests are handy enough. I just have jenkins doing a fresh database deploy and simulator database deploy and starting the simulator. It then goes on to execute a configuration matrix job just like your smoke tests but against the started box. When the tests get completed it calls a final job to just stop the jetty server. To get my current local pipeline going on up there it probably wouldn't require a lot since you have all the build tools/dependencies installed. I am doing static analysis of the code before the integration tests using sonar source... It requires a jenkins plugin and a sonar source daemon running. There's a sample on their demo of cloudstack code analysed but they leave out a lot of the checks. http://nemo.sonarsource.org/dashboard/index/440802. For speed purposes I've only been doing the analysis on the ldap plugin, a full check took a good hour. My .jenkins folder is roughly 11.5gb. If your interested on getting it up there I can schedule it for next week? There's a few small things I just want to clean up. Screenshots: http://ianduffy.ie/cloudstack/jenkins/ (See screenshot3 for a list of the tests that fail on the simulator)
