Ritu - you're correct. The plugin code at this point does not get tested by our CI without the hardware. It has been the onus of the contributor of the plugin to test against the hardware.
Because the project cannot afford to purchase, deploy and test against every piece of hardware we depend on the volunteer community to help out. You are encouraged to write Marvin tests/unit tests against your hardware and submit them to the repo along with the plugin code. In the event of the CI system including the hardware at least these tests can be run. Meanwhile, the project is discussing on hardware requirements in another thread which you responded to that AlexH @ Citrix started. If your company is interested in donating hardware to the ASF for the testing of its plugin, please keep an eye on how you can donate the same so your plugin may be tested adequately On Tue, May 27, 2014 at 10:27:05AM -0700, Ritu Sabharwal wrote: > Hello, > > Can someone please answer this question for me? > > Thanks & Regards, > Ritu S. > > -----Original Message----- > From: Ritu Sabharwal [mailto:rsabh...@brocade.com] > Sent: Wednesday, May 21, 2014 2:28 PM > To: dev@cloudstack.apache.org > Subject: How does Jenkins test new plugin for new device support? > > Hi, > > I am adding a new plugin for supporting new device. > Once the code is reviewed and committed to Git, would Jenkins run the > automated tests only for the management server and not the plugin code > because it would not have the new hardware to test it with. > > How does that happen ? > > Thanks & Regards, > Ritu S. -- Prasanna., ------------------------ Powered by BigRock.com