Integration with Jenkins 1.523 and RTC 4.0.2
Accepted answer
Hi Chung Lin,
I think what is probably happening, is that the buildResultUUID property on your Jenkins job is not getting created. It is the existence of this property value that the team concert plugin uses to decide if a new build result needs to be created. I don't recall if there's a problem in 4.0.2, but if you manually add a String property to your job, it should fix it.
Scott
I think what is probably happening, is that the buildResultUUID property on your Jenkins job is not getting created. It is the existence of this property value that the team concert plugin uses to decide if a new build result needs to be created. I don't recall if there's a problem in 4.0.2, but if you manually add a String property to your job, it should fix it.
Scott
Comments
Hi Scott,
That is exactly what we missed. But I'm not sure how to set the property environment variable in the build.xml file.
<property environment="env" />
<property name="buildResultID" value="${env.RTCBuildResultUUID}" />
This is what we use in the Build.xml file
buildResultUUID="${buildResultUUID}" instead of
buildResultUUID="${buildResultID}" from the complie-and-test example.
In this section, you should be getting the RTCBuildResultUUID environment variable, setting it to buildResultID and then subsequently passing it to the different Ant tasks.
Hi Scott,
Thank you for been so patient with me! It seems like whenever the build reaches -Ant build.xml file it started to create another build result. This happens is it because I run the Ant script in the post build task instead of using Invoke Ant?
Thanks
Chung
That sounds like a reasonable cause. I haven't tried that myself. But I believe we complete the build result by that point.
2 other answers
Hi Chung Lin,
Please take a look at https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin.
Scott
Please take a look at https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin.
Scott
Comments
Hi Scott,
That is the exact instuction that we followed, but we still get two build result if we trigger the job from RTC client.
This is what we see in the RTC build result.
please see below answer...
We know that if we trigger from RTC we will get the label test[154] and if we trigger from Jenkins we will get test#154. What we don't understand is why there is an additional build result if we just trigger the build ONCE in RTC?
Thanks
Chung