RTC 4.0.1 - Using Jenkins build from RTC - what is the property name in a build for indicating that this build is a personal build?
Accepted answer
Yes, you can pass the property via the Jenkins parameter. The property name is personalBuild, but it is a string property not a boolean one. But you should be able to manipulate it once you get it onto the Jenkins side.
EDIT: I just realized that the 'b' wasn't capitalized, I tried again and it interprets correctly with the boolean parameter too. So either one, but make sure its personalBuild! The parameters are case sensitive.
EDIT: I just realized that the 'b' wasn't capitalized, I tried again and it interprets correctly with the boolean parameter too. So either one, but make sure its personalBuild! The parameters are case sensitive.
~Spencer
One other answer
Hi Donald,
Unfortunately, there currently is no property to distinguish personal builds. However, this feature is in the plan we are currently working on.
246731: HPI: Request a personal build from Hudson/Jenkins is a child of 252582: [CCM] Improve Jazz SCM and Build integration with Jenkins - production quality.
If you haven't seen it, the richest integration you can currently achieve with RTC 4.0.1 and Jenkins is described in https://jazz.net/wiki/bin/view/Main/JazzScmWithJenkins.
I hope this helps for now,
Scott
Unfortunately, there currently is no property to distinguish personal builds. However, this feature is in the plan we are currently working on.
246731: HPI: Request a personal build from Hudson/Jenkins is a child of 252582: [CCM] Improve Jazz SCM and Build integration with Jenkins - production quality.
If you haven't seen it, the richest integration you can currently achieve with RTC 4.0.1 and Jenkins is described in https://jazz.net/wiki/bin/view/Main/JazzScmWithJenkins.
I hope this helps for now,
Scott
Comments
I stand corrected. Spencer's answer is, of course, correct. ;-) After following the steps in https://jazz.net/wiki/bin/view/Main/JazzScmWithJenkins. I was able to add a boolean value parameter, named "personalBuild", to the Jenkins job and it was properly passed into the ant task, just like buildResultUUID. Thanks Spencer.
Great - thanks - tried it and it works