We are running Jenkins 1.462 on an Ubuntu 10.04 LTS server, and we are using two plugins:
1. Gerrit trigger ( https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger) 2. SpiraTest (see http://www.inflectra.com/Documents/SpiraTestPlanTeam-Build-Server-Integration-Guide.pdf ) We noticed that Jenkins was receiving notifications of new changes in Gerrit and it was starting CI builds as a result. Gerrit was also receiving notifications that the Jenkins CI build had started, but no indication of the result of the CI build was ever received by Gerrit. We first reverted to one and then two versions older of the Gerrit trigger plug-in but this did not help. When we disabled the SpiraTest plugin, the Gerrit trigger plugin began to operate normally again. We contacted Inflectra (the SpiraTest vendor) with a description of the problem and some log files, and they were unable to provide any specific information, but they did make the following observation: We've looked at the logs and it looks like when you have the Gerrit plugin > installed, the Spira plugin is not able to run this call: spiraBuilder.getDescriptor() > which means that the Gerritt plugin is preventing the Spira plugin from > accessing the Spira-specific job configuration specified for the build. > We're not sure why that would happen. You should probably post a question > in the Jenkins forum to see if there are any known issues using multiple > plugins. It may be an issue with the Gerrit plugin... we're not sure. I have two questions: 1. What is the best way to debug/troubleshoot an issue like this? 2. Are there any known issues with having multiple plug-ins running as is being suggested here? Thanks, -- Larry Gadallah Elektrobit Inc.
