How to ensure that only tested code goes for release / production?
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
Defined in your Process Configuration's Team Configuration -> Operational Behavior
Comments
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???
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