Introduces an effective method to implement code synchronization between multiple stream in the RTC

The Rational Team Concert (RTC) is one of the most popular code management tools, but for source code synchronization on multiple stream, most http://www.aliyun.com/zixun/aggregation/7155. HTML "> Developers are repeatedly submitting code on each stream and manually guaranteeing synchronization, which undoubtedly increases the cost of our development. This article will introduce an effective approach to code synchronization between multiple stream lines in the RTC, reducing the cost of duplicate-commit code and avoiding the pitfalls of duplicate-commit code.

Stream (stream) is an important member of the Jazz source code management system, which embodies a version of the project development, consisting of one or more component (components). The creation of a stream allows team members to share and manage code among different versions, to meet the needs of code management in Project iterative development, and to promote better collaboration among team members. A component is the basic unit of code sharing and management, consisting of a file or folder in which team members can share code by using components in the stream.

Multiple Stream application Scenarios

At present, iterative development is very common in software development, and project development often involves two or more versions. That is, the development of the next version of the software, which is not yet published, will require the project developer to maintain multiple versions of the software at the same time. In particular, a flaw needs to be addressed on multiple versions so that code synchronization on these different versions of the software becomes the day-to-day work of team developers. How to simplify the process of code synchronization, improve the efficiency of multiple software version code synchronization and reduce the number of defects caused by code synchronization in multiple software versions is of great significance to reduce software development cost and improve software quality.

RTC support for multi-stream code synchronization

Source code management and sharing is an important part of project development, and RTC, as the main source control tool, provides a good mechanism for project source management and sharing. In the actual project development process, the project owner needs to create a stream on a remote jazz server where the project developer creates its own version library workspace based on this stream on a remote jazz server. In addition, developers need to create their own local workspaces on the local machine. The developer synchronizes the changes in the local workspace to their own version library workspace on the remote Jazz server through the Check-in operation, synchronizing the code of the Remote version Library workspace with the Deliver operation to the team-shared stream. Other team members synchronize the code from the stream to their own remote version library workspace through the Accept operation, and download the source code from the version library workspace to the local workspace through the Load operation. As such, the RTC can manage multiple stream and share it efficiently, and its specific source control and sharing mechanisms are shown in Figure 1:

Figure 1. Multi-stream source code management and sharing mechanism in RTC

Through the RTC in the source code management and sharing mechanism can be seen, if no modification and configuration, on multiple stream, the developer can only by maintaining the source code on each stream, and on these stream code back and forth to replicate to multiple stream source synchronization, This undoubtedly increases the cost of source code for maintaining and synchronizing multiple stream. In fact, the RTC can simplify source code synchronization on multiple streams by changing the corresponding flow target (target stream pointing) to effectively improve the efficiency of the project development.