dmmckinn 1200006SCS Visits (312)
A full list of fixes is available in the following documents:
Full Collaborative Lifecycle Management releases are available on Jazz.net: http
dmmckinn 1200006SCS Visits (811)
Sharing a list of the latest Continuous Engineering fixes that were recently released.
A full list of fixes is available in the following documents:
CLM releases are available on Jazz.net: http
dmmckinn 1200006SCS Visits (1251)
Program Board - Rational Team Concert 126.96.36.199
Program Board - Rational Team Concert 188.8.131.52 - This video demonstrates the new Program Board feature available in Rational Team Concert 184.108.40.206.
A new Program Board application is available from the plans menu. The Program Board shows the relationship between blocked by and depends on relationships for a set of work items scoped to a given timeline and project. It is useful for quickly identifying if there is a work item in your project that has a dependency on another work item but is attempting to be delivered or planned for a later sprint. In SAFe methodology, the Program Board provides transparency and visibility of the dependencies and enables the organization to address these by ensuring that features are delivered early enough in various sprints to avoid delays in delivery. The Program Board graphical visualization of dependencies can be used with any methodology (not just SAFe) that has parent child relationships and uses the blocked by and depends-on feature of work items to denote dependencies.
Note: If you have seen the RTC 6.0.6 technical preview of this feature, you will notice a considerable amount of changes in this release.
For additional information see:
Query Organization Using Tags - Rational Team Concert 6 0 6 1
Query Organization Using Tags - Rational Team Concert 6 0 6 1 - This video demonstrates the new web-based tagged queries feature in Rational Team Concert 220.127.116.11
This release adds the ability to organize work item queries by using tags. This feature is available as a technical preview. This feature supports grouping queries by tags on the My Queries and Shared Queries tabs. The tags can represent a hierarchy of folders. For example, the tag 18.104.22.168 / iFix003 / verification (release / iFix / type) displays with a root of 22.214.171.124, a child iFix003, and a nested child verification. You can organize your queries with new tags or existing tags.
For more details on the feature, see [CCM] Query organization using tags in web client - Technology Preview (472270)
To provide feedback on the feature, add a comment in [CCM] Query organization using tags in web client GA (474454)
dmmckinn 1200006SCS Visits (876)
This article provides guidance on using Rational Team Concert (RTC) as a source code management system in Jenkins jobs.
What is covered in the article:
dmmckinn 1200006SCS Visits (1016)
dmmckinn 1200006SCS Visits (1389)
Sharing some of the latest videos on Model Based Systems Engineering (MBSE) which include a brief introduction and demonstrations.
MBSE Introduction - This short video gives a brief overview of the capabilities and benefits of Model Based Systems Engineering with IBM Engineering Lifecycle Management
dmmckinn 1200006SCS Visits (1377)
Are you looking to understand more about how Work Items, Planning, Build, SCM and other concepts of Rational Team Concert (RTC) integrate?
The Rational Team Concert process fundamentals wiki provides a basic introduction of the underlying concepts of RTC and provides information to help you understand some of the basic fundamentals that will help to start and customize a new project. [Read more…]
dmmckinn 1200006SCS Visits (1529)
dmmckinn 1200006SCS Visits (1555)
Configuring Rational Team Concert to establish a global configuration context for work item links - Sharing a recent article by Kathryn Fryer, a Solution Architect at IBM, that describes how to configure Rational Team Concert (RTC), so users can link work items to specific versions of lifecycle artifacts. The article focuses primarily on links from Rational Team Concert to Rational DOORS Next Generation requirements and Rational Quality Manager test artifacts.
Arun K Sriramaiah 2700076GE8 Visits (1978)
Avoid using the custom attribute ids for Voting Feature implementation in IBM Rational Team Concert (RTC).
Below are a few issues that might occur in-case if you use the custom attribute ids which is not recommended.
Arun K Sriramaiah 2700076GE8 Visits (2293)
Navigate to a repo workspace on a stream (where that old version was baselined), select component in a repository workspace or stream in the Team Artifacts window and click on "Replace with".
Using the server setting “Server Default for Line Delimiter Handling” = NONE and usage limitation and understanding
Arun K Sriramaiah 2700076GE8 Visits (1863)
You may have noticed that there is a new feature in RTC 6.0.5 regarding Keyword expansion.
It may only be from the CLI and builds.
There is this statement:
2. How is the Keyword expansion enabled for a load operation if it is only used for the CLI and builds?
3. Does this mean the Keyword expansion is enabled for a load operation using the Eclipse client?
Arun K Sriramaiah 2700076GE8 Visits (2533)
Unidirectional & Bi Directional flow controls in IBM Rational Team Concert (RTC) Streams ( SIT \ UAT\ PROD) and Best Usage.
Below is one of the example for creating a RTC streams ( SIT \ UAT\ PROD) code delivery
Best usages & control of smooth code delivery between RTC streams (SIT, UAT and Prod)
Note: One of the best ways is to make sure SIT,UAT,Pre-PROD and PROD should be Unidirectional flows, so that it will not affect the existing codes.
The process is:
Below are a few things should be taken care of for smooth change flow.
1) The more frequently that you accept and deliver (assuming that your deliveries never break the product)
2) Merge in a small set of changes than a large set of changes.
3) The flow targets of a workspace have no effect on whether or not a change set shows up as ready to be accepted by other team members who share the same flow target. It is only when you have actually delivered
4) If you don't have any latest common changes, there shouldn't be any conflicts
5) A delivery of the code is made from the Module Streams to the Main Development stream.
Note: In case for the above situation if you find the conflict between streams. Please refer to the below blog.
Arun K Sriramaiah 2700076GE8 Visits (3528)
Enabling the RepoDebug service for Jazz Team Server (JTS) and Rational Team Concert (RTC) WebSphere Application Server (WAS) Liberty application server
The debug service is a general-purpose service that serves as the central location for finding various REST APIs that are useful for debugging. It was introduced into Jazz Foundation in v4.0.6 and is available for all JAF-based web applications.
Please refer the RepoDebug wiki for more details.
One of the best ways to have the specific version changes (change Set) into the RTC Repository workspace (Sandbox)
Arun K Sriramaiah 2700076GE8 Visits (1719)
One of the Best ways to have the specific version changes (change Set) into the Rational Team Concert (RTC) Repository workspace (Sandbox)
Please find the below scenario and use case as an example:
1) UserA Eg: Hello.java created 20 version
2) UserA <Lock> the file hello.java version.
3) UserA Repository worksapce Set Flow target <Bi-Directional> to Stream
Note: UserB needs only Specific Version into the Repository workspace.
4) UserB Repository workspace Set Flow target <Uni-Directional> (incoming) from Stream.
5) UserB Repository workspace Check the <Pending Changes> into the Stream.
6) UserB Repository workspace Select the Specific (for example, Hello.java version 10 ) <Change Set> and <Accept> the changes from <Pending Changes>.
7) UserB Repository workspace Select the Specific option <Merge Initial Change Sets>
8) UserB Repository workspace Opens the <Change to Merge Editor> under the < Resulting Change Set > Click <Complete> and <Ok> . Closing Editor click <ok>
Note: UserB gets to see the specific changes in the UserB Repository Workspace and Workspace Changes will not flow into the Stream since its Unidirectional changes. Also, the file can’t be modified since it is locked by UserA.