Issue Type: Bug Bug
Affects Versions: current
Assignee: Unassigned
Components: jiratestresultreporter
Created: 02/Jul/13 7:32 AM
Description:

Hello,

I've stumble upon a problem running fresh unmofified Atlassian JIRA v6.0.3#6099 and Jenkins 1.520

I've tried the plugin agaist the company's Jira installation but I've got the same error.

It seems that the REST request in mailformed (status: 400)

JiraTestResultReporter DEBUG Creating issue in project AUTOMATION at URL http://localhost:9000/rest/api/2/issue/

JiraTestResultReporter INFO Reporting issue.
JiraTestResultReporter DEBUG statusLine: HTTP/1.1 400 Bad Request

JiraTestResultReporter DEBUG statusCode: 400

ERROR: Publisher JiraTestResultReporter.JiraReporter aborted due to exception
java.lang.RuntimeException: JiraTestResultReporter ERROR Failed : HTTP error code : 400
at JiraTestResultReporter.JiraReporter.createJiraIssue(JiraReporter.java:188)
at JiraTestResultReporter.JiraReporter.perform(JiraReporter.java:108)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
at hudson.model.Run.execute(Run.java:1618)
at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:247)
Finished: FAILURE

I suggest it's because of incompatiblity between the some of the request fields and the Jira ones.JiraTestResultReporter

JiraTestResultReporter

JiraTestResultReporter

JiraTestResultReporter DEBUG ----------------------------
JiraTestResultReporter DEBUG projectKey: AUTOMATION
JiraTestResultReporter DEBUG errorDetails: No alert is present (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 2.63 seconds
Build info: version: '2.32.0', revision: '6c40c187d01409a5dc3b7f8251859150c8af0bcb', time: '2013-04-09 10:39:28'
System info: os.name: 'Windows Server 2008 R2', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_17'
Session ID: e97ecf43-52a8-40ed-ac0e-aeec6d4a6a8e
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities
Unknown macro: {platform=XP, databaseEnabled=true, cssSelectorsEnabled=true, _javascript_Enabled=true, acceptSslCerts=true, handlesAlerts=true, browserName=firefox, browserConnectionEnabled=true, nativeEvents=true, webStorageEnabled=true, rotatable=false, locationContextEnabled=true, applicationCacheEnabled=true, takesScreenshot=true, version=17.0.6}

JiraTestResultReporter DEBUG fullName: backoffice.autoreferrals.DuplicateBetPlacedThatHadTimedOutWhileWaitingForCustomerAcceptanceTest.testDuplicateBetPlacedThatHadTimedOutWhileWaitingForCustomerAcceptance
JiraTestResultReporter DEBUG simpleName: DuplicateBetPlacedThatHadTimedOutWhileWaitingForCustomerAcceptanceTest
JiraTestResultReporter DEBUG title: Case Result: testDuplicateBetPlacedThatHadTimedOutWhileWaitingForCustomerAcceptance
JiraTestResultReporter DEBUG packageName: backoffice.autoreferrals
JiraTestResultReporter DEBUG name: testDuplicateBetPlacedThatHadTimedOutWhileWaitingForCustomerAcceptance
JiraTestResultReporter DEBUG className: backoffice.autoreferrals.DuplicateBetPlacedThatHadTimedOutWhileWaitingForCustomerAcceptanceTest
JiraTestResultReporter DEBUG failedSince: 31
JiraTestResultReporter DEBUG status: FAILED
JiraTestResultReporter DEBUG age: 1
JiraTestResultReporter DEBUG ErrorStackTrace: org.openqa.selenium.NoAlertPresentException: No alert is present (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 2.63 seconds
Build info: version: '2.32.0', revision: '6c40c187d01409a5dc3b7f8251859150c8af0bcb', time: '2013-04-09 10:39:28'
System info: os.name: 'Windows Server 2008 R2', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_17'
Session ID: e97ecf43-52a8-40ed-ac0e-aeec6d4a6a8e
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities

platform=XP, databaseEnabled=true, cssSelectorsEnabled=true, _javascript_Enabled=true, acceptSslCerts=true, handlesAlerts=true, browserName=firefox, browserConnectionEnabled=true, nativeEvents=true, webStorageEnabled=true, rotatable=false, locationContextEnabled=true, applicationCacheEnabled=true, takesScreenshot=true, version=17.0.6}at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:187)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:554)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:569)
at org.openqa.selenium.remote.RemoteWebDriver$RemoteTargetLocator.alert(RemoteWebDriver.java:848)
at EventMarket.modifyPricingMaxBet(EventMarket.java:87)
at DuplicateBetPlacedThatHadTimedOutWhileWaitingForCustomerAcceptanceTest.testDuplicateBetPlacedThatHadTimedOutWhileWaitingForCustomerAcceptance(DuplicateBetPlacedThatHadTimedOutWhileWaitingForCustomerAcceptanceTest.java:96)

Project: Jenkins
Priority: Blocker Blocker
Reporter: Atanas Kanchev
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to