Stream Best Practice - Integration -> QA stream flow
CLM 502
3 projects using 3 patterns for flowing stream to stream. Which is the Best Practice? How does Rational do it? Team #1 - They do a build in Integration. They then login as the build user and build workspace and accept any changes. They then flow up to the QA Stream. Team #2 - They do a build in Integration. They go to the pending changes view of the Integration Stream and flow changes to the QA stream. Then accept the changes from the QA stream. (Have not seen this for myself, but did not know this could be done.) Team #3 - They do a build in Integration. They then run their Int->QA build definition that doesn't "really" do a build, but flows to the QA stream. Is there a more accepted way than another? We know how to get the data up to QA, we just want ONE way to do it from now on... |
Accepted answer
There is actually another way which might fit better. There is a post-build deliver option for build definitions for flowing to another stream. The idea is if a build is run against Integration and its green, the post build deliver will automatically flow the changes up to another stream (QA). You can configure the criteria to allow the flow to the new stream.
If there is any objection to automating the process of delivery, then i would go with team 2 method as it allows the user to see the CS going to the QA stream.
~Spencer
Mahari Hill selected this answer as the correct answer
|
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.