On Thu, Jun 27, 2013 at 01:44:40PM +0100, Ian Duffy wrote: > > 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? >
The jenkins instance is mostly managed by committers and is outside the ASF infra. We do non-oss builds using non-oss binaries, so that's not a problem. > > 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. > So this would definitely be useful on our jenkins, you have access, so feel free to configure the job. Any backing hardware/virtual resources you need can be provisioned as reqd. > 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. The jenkins plugins can be enabled/installed. I'll try and look at the sonar source daemon over the weekend. > > 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. Thanks, let us know. > > Screenshots: > http://ianduffy.ie/cloudstack/jenkins/ (See screenshot3 for a list of > the tests that fail on the simulator) In case you're running the automated tests using the simulator, not all of them will pass since some of them require a physical hypervisor to be present. But most should work well on the simulator. The ones that pass on the simulator are tagged 'simulator' -- Prasanna., ------------------------ Powered by BigRock.com
