It's all about the answers!

Ask a question

Issue with RTC "teamFetch" Ant Task for Hudson Int


Tim Mulligan (22633214) | asked Sep 23 '10, 11:45 a.m.
retagged Aug 19 '12, 6:58 a.m. by Nhi P Ta (18841018)
Hi all,

Has anyone worked with the RTC "teamFetch" Ant task for Hudson integration yet?

We have encountered an issue with this RTC ant task which Hudson uses to retrieve code from RTC. The issue only happens when the RTC workspace contains more than one component having similar directory structures.

Were following the instructions here: http://jazz.net/library/article/350

We got the example to work with a single component stream but it is failing with a multiple component stream.

The issue is that RTC (via eclipse) allows multiple components having similar directory structures (e.g. src, test, build) to be loaded into a workspace because it includes the component name in the resultant workspace directory structure.

However the ant task used by Hudson called teamFetch does not include the component name in the resultant Hudson workspace and therefore conflicts/clashes occur during the load which cause the load to fail:

Here is a link to the RTC "teamFetch" ANT task reference:
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.team.build.doc/topics/r_teamfetch.html

Ideally, there should be an option to selectively load components, or to include the component name in the resultant loaded workspace directory structure.

<teamFetch>

For example, RTC eclipse creates this folder for the component "Component-1"

C:\Documents and Settings\<user>\workspace\Component-1\src

Yet the RTC "teamFetch" ANT task creates this folder (w/o Component name):

C:\hudson\workspace\RCT_Hudson\working-dir\src

This is OK if the stream contains only one component, but our app has 4 components with similar directory structures within each component (e.g. src, build, etc).

Any guidance or help would be most appreciated!

One answer



permanent link
Geoffrey Clemm (30.0k23035) | answered Sep 23 '10, 9:03 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Tim,

I believe what you want in the 3.0-RC0 "Create component folders on
load" feature (see
https://jazz.net/downloads/rational-team-concert/milestones/3.0RC0?p=news).

But I assume what you really want is a workaround for 2.0, right? If
so, I'm going to have to defer to an RTC build guru (it's probably going
to involve going to the RTC command line for at least part of it).

Cheers,
Geoff

On 9/23/2010 11:53 AM, timothy.mulligan wrote:
Hi all,

Has anyone worked with the RTC "teamFetch" Ant task for
Hudson integration yet?

We have encountered an issue with this RTC ant task which Hudson uses
to retrieve code from RTC. The issue only happens when the RTC
workspace contains more than one component having similar directory
structures.

Were following the instructions here:
http://jazz.net/library/article/350

We got the example to work with a single component stream but it is
failing with a multiple component stream.

The issue is that RTC (via eclipse) allows multiple components having
similar directory structures (e.g. src, test, build) to be loaded
into a workspace because it includes the component name in the
resultant workspace directory structure.

However the ant task used by Hudson called teamFetch does not
include the component name in the resultant Hudson workspace and
therefore conflicts/clashes occur during the load which cause the
load to fail:

Here is a link to the RTC "teamFetch" ANT task reference:
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.team.build.doc/topics/r_teamfetch.html

Ideally, there should be an option to selectively load components, or
to include the component name in the resultant loaded workspace
directory structure.

<teamFetch

For example, RTC eclipse creates this folder for the component
"Component-1"

C:\Documents and Settings\<user>\workspace\Component-1\src

Yet the RTC "teamFetch" ANT task creates this folder (w/o
Component name):

C:\hudson\workspace\RCT_Hudson\working-dir\src

This is OK if the stream contains only one component, but our app has
4 components with similar directory structures within each component
(e.g. src, build, etc).

Any guidance or help would be most appreciated!

Your answer


Register or to post your answer.