Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Work items included in Build results.

Hi, I am doing some test with RTC 2.0 Beta2 Build System and I am not
able to see included work items included in Build results. Same steps in
RTC 1.0.1.1 worked fine.

Is there anything new to do in 2.0 to include work items automatically
in Build results? what I do is create some work items, deliver changes
associating them to those work items, and execute the build. Although
the Build results show the change sets, it doesn't show the associated
work items. Am I missing anything?

Thanks in advance,

Chemi.

0 votes



2 answers

Permanent link
Chemi wrote:
Hi, I am doing some test with RTC 2.0 Beta2 Build System and I am not
able to see included work items included in Build results. Same steps in
RTC 1.0.1.1 worked fine.

Is there anything new to do in 2.0 to include work items automatically
in Build results? what I do is create some work items, deliver changes
associating them to those work items, and execute the build. Although
the Build results show the change sets, it doesn't show the associated
work items. Am I missing anything?

Thanks in advance,

Chemi.

Is anybody using last Beta 2 seeing this same behavior? I would like to
know if this is happening just to me, to decide if I open a defect or not.

Thanks in advance,

Chemi.

0 votes


Permanent link
Chemi wrote:
Chemi wrote:
Hi, I am doing some test with RTC 2.0 Beta2 Build System and I am not
able to see included work items included in Build results. Same steps
in RTC 1.0.1.1 worked fine.

Is there anything new to do in 2.0 to include work items automatically
in Build results? what I do is create some work items, deliver changes
associating them to those work items, and execute the build. Although
the Build results show the change sets, it doesn't show the associated
work items. Am I missing anything?

Thanks in advance,

Chemi.

Is anybody using last Beta 2 seeing this same behavior? I would like to
know if this is happening just to me, to decide if I open a defect or not.

Thanks in advance,

Chemi.

With Nick help we found the reason. Build process was using the same
Repository Workspace where the code changes were done. Creating a new
Repository Workspace pointing to the same stream than the other and
using it into the Build Definition did the trick.

Regards,

Chemi.

0 votes

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: May 25 '09, 2:01 p.m.

Question was seen: 4,496 times

Last updated: May 25 '09, 2:01 p.m.

Confirmation Cancel Confirm