It's all about the answers!

Ask a question

How to ensure that only tested code goes for release / production?


anup Gaur (1391335) | asked Mar 29 '14, 1:11 p.m.
retagged Jul 22 '14, 3:38 p.m. by Ken Tessier (84117)
How to ensure that only tested code goes for release / production. Can we define a best practice / implementation details, here including the steps in Rational Team Concert source control.

In the context of source control in RTC how do we ensure that source code that has passed test will go to production.
How can we implement this requirement in rational team concert. Do we have any process pre-condition rules to do this?

Accepted answer


permanent link
Mark Castro (74819) | answered Mar 30 '14, 9:08 a.m.
You could enforce Approvals for all delivers to your streams (requires that each change set has an associated work item, as well), with Approvers signing off only on tested code.

 Defined in your Process Configuration's Team Configuration -> Operational Behavior
anup Gaur selected this answer as the correct answer

Comments
Manoj Panda commented Jul 13 '14, 12:59 a.m.
JAZZ DEVELOPER

Hi Mark/Anup,
  I do agree but lets assume after all approval, the tested code deliver to production/release stream. Then next action point is the to do the build from release stream and deploy into production system.
How do we ensure than the build has been performed on release stream??
I do understand that we can use the build definition/engine provided by RTC but if the developer do the  build  using .net (VS), how can we keep track of that.
Simple question: How do we ensure that Application deployed on production system is the exactly same which was build from the release stream???


sam detweiler commented Jul 13 '14, 7:33 a.m.

this has to be all about process.

no developer should be able to run a build on the release stream. only the release team member/role.
and u never deploy anything from outside the release stream process.

you take a snapshot on the release stream build cycle.
if the build and test pass, then you create a a release candidate stream from the snapshot which then isolates the rest of the process from any ongoing changes.  you can build and deploy from the candidate stream after additional testing

One other answer



permanent link
Ken Tessier (84117) | answered Jul 22 '14, 3:38 p.m.
Here are some links on configuring operation behavior (preconditions and follow-up actions):

Your answer


Register or to post your answer.