Advice on best way to use RTC streams
![]() Hi I am in the process of taking over the SCM role for a large enterprise team of 150+ developers spread across multiple scrum teams using a mixture of technologies including Teradata, Oracle, PowerCenter, Aptitude, and scripts The current setup of RTC has two streams for each scrum team, one for development and one for test. We have a monthly release cycle so each month a release candidate is created and all scrum team test streams are merged one at a time into the release candidate stream. This release candidate stream then flows into a system integration test stream and a business acceptance stream before finally flowing into the production stream. 1 week is spent in system integration and 1 week in business acceptance Speaking to the teams and management i have so far identified a number of problems
1. Merging the code into the release candidate takes days as each stream has to rebase from the release candidate before merging and this is done sequentially.
I have been reading as much material as i can find on RTC looking at best practises and trying to understand how RTC differs from other versioning systems i have used such as Git and Perforce. There are plans to rampup the number of scrum teams but first we need to address a number of issues within the current process and i am looking for advice on how best to approach this
Kind Regards
|
One answer
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Jan 24 '17, 2:57 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Comments Thanks Ralph 1) I believe you are saying instead of doing the merge of the release candidate to the team stream and then bringing the merged code into the release candidate they should merge directly into the release candidate and resolve code conflicts there, Correct? Also they should do the merge as soon as they are "done" and not wait until the end of the sprint so that the effort to do the merges remains manageable 2) We will be conducting a retrospective around the latest release which had merge issues and will provide training and feedback if required 3) and 4) Agreed. I suspected this was the way it should be done What do you think about having all these environment streams? They have streams for the development teams that get merged to a team test stream for deployment into a dedicated test system. Then they have similiar environment streams for both System Integration (SIT) and Business Acceptance Test (BAT) environments once the release candidate has been fully merged. Shouldn't we get rid of these environment streams and instead deploy test systems from snapshots?
|
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.