Promote the snapshot from workspace to a stream
4 answers
Hi,
the advanced search https://jazz.net/search_results.jsp?q=promote+snapshot#page=0&type=&q=promote%2Bsnapshot
comes up with several discussions from the past. In https://jazz.net/forums/viewtopic.php?t=17552 we discussed using the SCM commandline http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.team.scm.doc/topics/r_scm_cli_snapshot_promote.html
that was introduced in 3.x. There is no ANT task available I am aware off.
The question I have is, why would you want to do that? Assuming you have one build workspace per build definition, you could keep the snapshots there and manually promote only the important ones to the stream. instead of having snapshots for every build on the stream you would have only the important ones.
the advanced search https://jazz.net/search_results.jsp?q=promote+snapshot#page=0&type=&q=promote%2Bsnapshot
comes up with several discussions from the past. In https://jazz.net/forums/viewtopic.php?t=17552 we discussed using the SCM commandline http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.team.scm.doc/topics/r_scm_cli_snapshot_promote.html
that was introduced in 3.x. There is no ANT task available I am aware off.
The question I have is, why would you want to do that? Assuming you have one build workspace per build definition, you could keep the snapshots there and manually promote only the important ones to the stream. instead of having snapshots for every build on the stream you would have only the important ones.
Does there any way to automatically promote the snapshot generating during build in the build repository workspace to a stream?
This isn't exactly what you are requesting, but it's similar, so I'll mention it here:
In RTC 4.0, if you are using the 'Post-build Deliver" option in a build definition, there is a new section in the UI called "Snapshot Owner". Using the options in this section, the build can now automatically set the deliver target as the owner of the snapshot created during the Jazz SCM pre-build phase. This makes sense when you are delivering 'all' component changes to a "green" stream; You would then want the snapshot to be owned by that stream so it's easier to find.