"Track Build Item" type
I am a little sketchy on what this type is actually for. I've found a couple of different explanations:
On Jean-Michel's blog http://jazz.net/blog/index.php/2009/10/22/making-agile-real/, it describes it as something used to coordinate between different teams:
In the RTC documentation under "Work Item Types," it is described as:
It also appears that the 3 states for this type are "In Progress," "Done," and "Abandoned."
Can someone from IBM describe how you use this work item type?
Thanks in advance,
Mike Johnson
On Jean-Michel's blog http://jazz.net/blog/index.php/2009/10/22/making-agile-real/, it describes it as something used to coordinate between different teams:
In our retrospectives we would often hear complaints about that other team. In order to avoid the blame game, and remove the friction between teams we added the Track Build Item and Adoption Item. These artifacts provide an explicit channel for cooperation on these two very important activities on our team. By making them explicit weve made it clear to the teams that succeeding and optimizing these two collaborative activities is a top priority.
In the RTC documentation under "Work Item Types," it is described as:
Typically created from a build result to track the fixes that are needed for a failed build
It also appears that the 3 states for this type are "In Progress," "Done," and "Abandoned."
Can someone from IBM describe how you use this work item type?
Thanks in advance,
Mike Johnson
4 answers
Hi Mike,
In Jazz Foundation, we use the track build work item type to track our integration (or product level) builds over a given time period. This helps different component teams coordinate on fixing build errors and test failures, and results in a stable build which satisfies each team's goals for the builds time frame.
There are two main practical uses for the Track Build item. First, when a build's status is red, the problem can be investigated and the cause posted in the Track Build item. This allows each team to see why the build is red, and to track the status of any fixes that are being prepared. Second, when a green build is presented as a possible candidate for a weekly build (or milestone build), each team is responsible for testing their component using the candidate build files. Approvals for the build are added for each Team Lead, and they (or a team member) must fetch the build and test their component on it, as well as any fixes or features they have delivered since the last build. If there are problems they can reject the build, and work within their team or with other components on fixes to be included in the next build, which will then be put forward for approval.
In Jazz Foundation, we use the track build work item type to track our integration (or product level) builds over a given time period. This helps different component teams coordinate on fixing build errors and test failures, and results in a stable build which satisfies each team's goals for the builds time frame.
There are two main practical uses for the Track Build item. First, when a build's status is red, the problem can be investigated and the cause posted in the Track Build item. This allows each team to see why the build is red, and to track the status of any fixes that are being prepared. Second, when a green build is presented as a possible candidate for a weekly build (or milestone build), each team is responsible for testing their component using the candidate build files. Approvals for the build are added for each Team Lead, and they (or a team member) must fetch the build and test their component on it, as well as any fixes or features they have delivered since the last build. If there are problems they can reject the build, and work within their team or with other components on fixes to be included in the next build, which will then be put forward for approval.
No, this is not currently supported.
It is requested in work item 96472. Please feel free to add a comment
to indicate your interest/support.
Cheers,
Geoff
On 1/4/2012 3:53 AM, mickey_roash wrote:
It is requested in work item 96472. Please feel free to add a comment
to indicate your interest/support.
Cheers,
Geoff
On 1/4/2012 3:53 AM, mickey_roash wrote:
Hi ,
I their a way to run few different external compare editor,
each one for different file type or file extension ?
I am using RTC 3.0.1 .
Thanks,
Mickey