Integration with Jenkins 1.523 and RTC 4.0.2
My question is when ever we trigger a build from RTC to Jenkins we will have two build result, but if we trigger the build from jenkins there would be just one. Is there a solution for this?
Our Setup:
|
Accepted answer
Scott Cowan (966●3●10)
| answered Dec 09 '13, 11:54 a.m.
JAZZ DEVELOPER edited Dec 09 '13, 11:55 a.m.
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 
chung Lin selected this answer as the correct answer
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
|
This is what we see in the RTC build result
|