Deliver all changesets associated with a particular component for approved work items at a particular state
Hello,
We have a development stream where there are no strict gates for delivering files from workareas into the stream other than you must associate a work item. At a point in time we want to deliver all changesets associated with approved work items to a verification stream from the development stream for the components contained in the development stream, the verification stream flows from the development one, we do not want any changes associated with unapproved work items. How best would I achieve the stated aim. I would like to automate this as my criteria are fairly fixed. Thanks for any help
Richard
2 answers
If that does not work for you then you have to write a custom precondition to achieve this functionality.
Comments
Hi Ralph,
Ran out of comment space so incorrectly adding my comment as an answer
Thanks for the usual good advice, maybe I should ask the question in a more generic way. You may remember me from my Dimensions to RTC migration questions. In Dimensions the verification of the work items had a direct affect on the state of the files and whether or not the particular version appeared in a formal build or not. We are all about replicating this sort of function in RTC, but I at least am open to different ways of achieving it.
So whilst the work items associated with changes go through a formal change the delivery of actual source code/ file changes is not governed by changing their state. I need some way of distinguishing in an automated fashion between those changes that are reviewed and approved and those that are work in progress/ unapproved. I want to be able to move approved changes to a particular stream but be prevented from moving unapproved changes, RTC does not seem to lend itself to this sort of requirement or I am quite possibly missing something. How would you achieve what I require both automatically (ideally) and manually.
Re my proposed work item save follow up action: I see your point, it would not be feasible without asking for the stream you are coming from along with cross referencing the pending changes from that stream to any flowed to stream, but in some circumstances this sort of information provided on a pre-condition when changing to a resolved/ deliver to config area state might be acceptable to my customer, acceptable answers on the precondition would then initiate a follow up action to deliver the changesets to the formal stream.
Thanks for any ideas/ advice
Richard