It's all about the answers!

Ask a question

Why am I suddenly getting this error when trying to build from Jenkins?


Paul Bailey (1312) | asked Jun 08 '16, 2:06 p.m.
edited Jun 11 '16, 5:30 p.m. by David Lafreniere (4.8k7)
After restarting our Jenkins system for an administrative reason all our builds are now failing with this error:

Started by user SVC_Jenkins
[EnvInject] - Loading node environment variables.
Building on master in workspace /var/lib/jenkins/jobs/remote-administration-monitor/workspace
RTC : checkout...
RTC : Build initiated by request from RTC
FATAL: RTC : checkout failure: null
java.lang.UnsupportedOperationException
    at java.util.Collections$UnmodifiableCollection.add(Collections.java:1075)
    at com.ibm.team.build.internal.hjplugin.RTCScm.checkout(RTCScm.java:1041)
    at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
    at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
    at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
    at hudson.model.Run.execute(Run.java:1738)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:410)
ERROR: RTC : checkout failure: null
An attempt to send an e-mail to empty list of recipients, ignored.
Finished: FAILURE

We are using:
Jenkins 1.651.2
RTC Build Toolkit 4.0.2
Team Concert Plugin 1.1.9

When we test the connection to RTC through the Jenkins dashboard we see "Connection test was successful"

Our sys admin is out for medical reasons so I'm trying to help out with getting the builds up and running again. Did we not restart everything we need to? Any particular service we should check?

Thanks in advance!

Accepted answer


permanent link
Sridevi Sangaiah (59179) | answered Jun 13 '16, 12:11 a.m.
JAZZ DEVELOPER
Hi,

https://issues.jenkins-ci.org/browse/JENKINS-33467 is the one that triggered https://issues.jenkins-ci.org/browse/JENKINS-34117. The fix for the issue 33467 has been included in 1.651.2 - https://jenkins.io/changelog-stable/.

So, upgrading the Team Concert plugin to 1.2.0.0 should fix the Exception.

Thanks,
Sridevi

Paul Bailey selected this answer as the correct answer

One other answer



permanent link
Donald Nong (14.5k414) | answered Jun 08 '16, 9:35 p.m.
Are you aware of this bug?
https://issues.jenkins-ci.org/browse/JENKINS-34117

It appears that you need to use the Team Concert Plugin 1.2.0 to resolve this issue.

Comments
Paul Bailey commented Jun 09 '16, 12:53 p.m. | edited Dec 30 '16, 5:00 p.m.

It appears that the referenced bug is a result of a change in Jenkins 1.655. I'm using 1.651 so I wouldn't expect that to be the issue (unless I'm misunderstanding that bug).

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.