Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

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

Questions
Tags
Users
Badges
anup Gaur
(139●24●44) retagged
Jul 22 '14, 3:38 p.m.
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?

0 votes

2 answers
5,716 views
0 votes

Accepted answer

Permanent link
Mark Castro
(74●12●19) 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

0 votes

Comments
Manoj Panda
JAZZ DEVELOPER Jul 13 '14, 12:59 a.m.
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
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
(841●1●7) Jul 22 '14, 3:38 p.m.
Here are some links on configuring operation behavior (preconditions and follow-up actions):

0 votes

Your answer

Register or log in to post 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 1,381

Question asked: Mar 29 '14, 1:11 p.m.

Question was seen: 5,716 times

Last updated: Jul 22 '14, 3:38 p.m.

Confirmation Cancel Confirm