官术网_书友最值得收藏!

Change sets

A change set is a collection of changed resources in a single component, which can be either checked-in and delivered or suspended till a later time. Change sets flow between a repository workspace and its flow targets. Workspaces usually have at least one flow target and many have more than one.

Change sets are classified as outgoing when they are present in a local workspace but not in its flow target. In a similar way, change sets are classified as incoming when they are present in a flow target but not in the local workspace itself. Flow targets specify the sources and destinations of incoming and outgoing change sets. Streams have flow targets only if they are part of a stream hierarchy.

Once team members change project artifacts, the changes need to be applied to the streams so that the entire team can see the changes. Of course, in this case, the other team members need to accept the incoming change sets. In general, we refer to "change flow" to define the flow of the changes from the repository workspace to the flow targets. These flow targets can be one or more streams.

Let's see a simple scenario of making a change in the BookManager Doc component, then contribute it to the associated flow target:

  1. Make a change to the README.txt file in the BookManager Doc component and save the file from the Eclipse client.
  2. The Rational Team source control knows the file change and adds this change to the Pending Changes view as an unresolved change.
  3. You can now check-in and deliver the change set. In our case, we create a new change set from the context menu of the unresolved change set by selecting Check-in | New Change Set.
  4. Once the change set is created, we can edit the comment, as well as choose from several other options, as follows:
    • Open the change set in the Change Explorer to view all the affected files.
    • Deliver the change set to the flow target so that the changes are applied to the stream and is visible to the entire team.
    • Suspend a change set to remove it from the repository workspace and unload it from the local workspace. However, the code is preserved in the repository so that it can be restored when we want to resume work on it.
    • Discard a change set, when we think that the change set is invalid or could cause a problem to the source code. We can discard either an outgoing change set or an accepted change set.
    • Reverse a change set to remove the captured changes. The reverse operation on a change set creates a patch. If we want to undo the delivery of a change set, we can create a new change set that reverses all the changes in it and then deliver the reversed change set.
    • Deliver and resolve work item action will deliver the change set to the flow target and, at the same time, associate the change set to the work item.
    • Submit for review action sends a message to the assigned reviewer for the module. To submit the change set for review, we must associate the work item to a change set.
    • Complete action marks the Change set as complete. Remember that the change set is in "working" state until it is explicitly marked as complete.
    • Associate work items to the change set to have a traceability of changes.
  5. Select the change set and deliver it to the following target. Now the rest of the team members will be able to see the delivered change set.

These steps complete the roundtrip between changing a resource and finally making it available to the team through flow targets.

主站蜘蛛池模板: 二连浩特市| 广德县| 夏河县| 桐柏县| 海门市| 佳木斯市| 天镇县| 吉安县| 桐梓县| 石楼县| 凤庆县| 阿鲁科尔沁旗| 凭祥市| 云龙县| 扎囊县| 昌都县| 东阿县| 德安县| 朝阳区| 昌都县| 红桥区| 木兰县| 石首市| 天祝| 彭州市| 故城县| 东乌| 吴桥县| 兴安盟| 宁化县| 仙居县| 白山市| 昌邑市| 那坡县| 简阳市| 儋州市| 全南县| 太康县| 蚌埠市| 千阳县| 克山县|