It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×6,076

question asked: Jun 11 '13, 4:49 p.m.
question was seen: 5,807 times
last updated: Jun 12 '13, 11:12 a.m.

Related questions

FAQ - How this Forum works

Jenkins integration

0
SUNIL KUURAM (64●3●19●23) | asked Jun 11 '13, 4:49 p.m.
Hello,

I understand RTC build properties can be passed to Hudon/Jenkins via build parameters. However, RTC seems to fail with in-appropriate message  such as below when an invalid property is passed to a choice list parameter in Jenkins  and build launched -

Error starting Hudson/Jenkins build for job "XXXXXX":
java.io.IOException: Error submitting build to Hudson/Jenkins. Expected code 200 OK but received code 500 with message: Internal Server Error
    at com.ibm.rational.hudson.team.internal.service.HudsonBuildLoopRunnable.startHudsonBuild(HudsonBuildLoopRunnable.java:272)
    at com.ibm.rational.hudson.team.internal.service.HudsonBuildLoopRunnable.processRequest(HudsonBuildLoopRunnable.java:141)
    at com.ibm.rational.hudson.team.internal.service.HudsonBuildLoopRunnable.run(HudsonBuildLoopRunnable.java:111)
    at com.ibm.rational.hudson.team.internal.service.HudsonBuildLoopScheduledTask.runTask(HudsonBuildLoopScheduledTask.java:43)
    at com.ibm.team.repository.service.async.AbstractAutoScheduledTask.executeTask(AbstractAutoScheduledTask.java:87)
    at sun.reflect.GeneratedMethodAccessor360.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
    at $Proxy879.executeTask(Unknown Source)
    at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:136)
    at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:99)
    at java.lang.Thread.run(Thread.java:736)


Any work arounds? probably not, I will create a defect.

Thanks
Sunil

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Scott Cowan (966●3●10) | answered Jun 12 '13, 11:11 a.m.
JAZZ DEVELOPER
Hi Sunil,

Thank you for opening the work item, RTC build fails with inappropriate message when invalid parameter passed to Jenkins (268708)

We will need more information to diagnose the problem.  Would it be possible to capture the HTTP request details and/or the error logged in the Jenkins server log?

Thanks,
Scott
0
permanent link
Heather Fraser-Dube (451●2) | answered Jun 12 '13, 11:12 a.m.
JAZZ DEVELOPER
The 500 is coming from Jenkins, To see, try running your build using the rest api  (to get the link, In Jenkins, click on Rest API at the bottom of the configuration page for your job). example: http://your.server.com:9080/jenkins/job/myJob/buildWithParameters?myChoiceParm=BadValue

You could try making your parameter a string, then any value will go through.

You can also try the new Jenkins integration (Team Concert plugin). If you use that with your RTC build definition, you don't need to define any parameters on your Jenkins Job and the parameters from the build request will still be available in your Job's env. Of course if you do define a choice parameter on the job, the build definition or when you make the request will still need a good value.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.