It's all about the answers!

Ask a question

Team Concert Jenkins Plugin/RTC 4.0.5 - Cannot get Jenkins tutorials to work

David Arnone (111619) | asked Mar 05 '14, 3:20 p.m.
edited Mar 05 '14, 3:26 p.m.


I am working through the following Jenkins tutorials using Windows 7/RTC 4.0.5

and I am unable to get either to work.  I have been to the simplest HelloWorld example setup twice.  When I activate submit build, RTC build is pending and Jenkins is never triggered.  Has anyone else encountered this problem?

David Arnone commented Mar 05 '14, 5:57 p.m.

So I have gotten Nick Edgar's example documented here: to run from the Jenkins side - that is "Build with Parameters" from within Jenkins runs and reports back to RTC.  But requesting the build from within RTC does not trigger Jenkins yet everything on the RTC side checks out.  The engine connection to Jenkins is successful and the build definition retrieves all of the available jobs.  There is no authentication so that is not the problem. 

Nick Edgar commented Mar 06 '14, 10:45 a.m.

Hi David, is there anything relevant in the server-side log for RTC (ccm.log)?

David Arnone commented Mar 08 '14, 10:45 a.m.

Request build puts the build into the pending state and nothing from that action is written tot the ccm.log file

2 answers

permanent link
David Arnone (111619) | answered Mar 07 '14, 10:50 p.m.
 I have been working this through an IBM PMR (I do not remember the number off hand and will post it later
But is far what we have determined is if Jenkins is executed via a command line against the jenkins.war file
the examples work.  When jenkins.war gets dropped into the webapps folder of Tomcat the examples do not
work.  More investigation is required.  I will post more details later.

David Arnone commented Mar 08 '14, 10:14 a.m.

When running jenkins from the command line as:

java -jar jenkins.war --httpPort=7080 >logs\jenkins.log 2>&1
The examples work but when the jenkins.war file is dropped into a Tomcat webapps folder RTC does not trigger jenkins.  The build remains indefinitely in a pending state.
The PMR on this is 38655.

sam detweiler commented Mar 08 '14, 10:28 a.m.

what port is tomcat running on?  7080? 

the examples depend on that 7080 config.

permanent link
David Arnone (111619) | answered Mar 08 '14, 5:15 p.m.
According to IBM support, Specer Murata provided the answer in a similar post:

but I have not yet tried it.  The answer from Spencer was

"There is a defect where RTC used to allow automatic address forwarding in previous releases so something like localhost:8080/hudson would redirect to localhost:8080/hudson/ but does not anymore, so the trailing slash has to be explicit in 4.0.3.  The authenticating user in Hudson also must be allowed to update the build job as we require a build parameter be added to RTC enabled Hudson jobs.  So I would recommend granting those permissions or trying the integration with an Hudson admin user first so it can setup the parameter and then change it to the build user."

Go figure..  I will try it later.

sam detweiler commented Mar 08 '14, 6:27 p.m.

yes, mine was just stalled (on 4.0.5) because of the missing trailing slash..
and I had to make an admin user on Jenkins

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.