How to customize the snapshot name created by automated build?
Qunfeng Wang (42●1●7●10)
| asked May 09 '13, 1:09 a.m.
edited May 09 '13, 5:13 p.m. by Spencer Murata (2.3k●11●59●71)
Both my source code and build are managed by RTC. I find a snapshot will be created automatically with each build. It has a name like MyBuildDefinition_20130430-0852. The name makes little sense. I'd like to customize it to MyBuildDefinition_1.0.0.123. How can that be done in RTC?
|
Accepted answer
Hi,
to make the build behave differently, you would have to write a build participant as per the description in this forum entry. The Build FAQ also points to that entry. It might be easier and more pragmatic to simply rename the snapshot after creation. You can do this manually by following the link to the associated snapshot from the build results object, opening the snapshot and simply replacing its name, then save. Possibly a post-build participant which renames the snapshot would be able to automate this. But it is probably as much work to simply write a new build participant. Does this help? Then please mark it as accepted answer. - Arne Qunfeng Wang selected this answer as the correct answer
Comments 1
Spencer Murata
commented May 09 '13, 5:14 p.m.
| edited May 09 '13, 5:17 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
I would add that if you want that functionality out of the box you can open a RFE so it can be considered for inclusion in a later release. However currently there is no automated out of the box solution for what you describe. I would say that the actual name of snapshot is not THAT important since it would be linked to the build result which would match your version criteria for the snapshot. So changing your work flow from looking at the stream history to pick out the build snapshot, to finding the relevant build result and then navigating to the snapshot associated to that build.
Qunfeng Wang
commented May 10 '13, 1:19 a.m.
Thanks for your answer Arne!
|
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.