It's all about the answers!

Ask a question

Which local folder is in use during the build?


Jirong Hu (1.5k9295258) | asked Jul 07 '11, 10:11 a.m.
Hi

Please look at the image below:

1. In build definition, the load directory is C:\Program Files\IBM\TeamConcertBuild\buildsystem\buildengine\eclipse\build
2. The build workspace is JUnit Integration Stream Workspace.
3. If I right-click the above workspace --> Load, it shows me a different local folder, which is D:\workspace\sandbox
4. Which local folder is actually used during the build (assume there is a load action in the build script)? If every workspace already has a local folder, why need to define in build definition?



https://lh6.googleusercontent.com/-TfFx5oYkf0M/ThW89JtIe3I/AAAAAAAAEl4/YxXm-kUMsMU/s1440/build%252520local%252520folder.png

3 answers



permanent link
Walter Mansur (63613017) | answered Jul 07 '11, 1:27 p.m.
Hi Jirong,

You did not say what version you are using. In v2.0.0.2, iFix6, that string in the "Load Directory: field needs to look something like this: ${propertyName}. It says so in the description above it:

Properties can be referenced using ${propertyName}.

I believe that you can also put an actual path name in that field (i.e., C:\build).

Perhaps the build thinks that since nothing is there, it puts the build results in your "sandbox". Just a thought.

-Walter

Hi

Please look at the image below:

1. In build definition, the load directory is C:\Program Files\IBM\TeamConcertBuild\buildsystem\buildengine\eclipse\build
2. The build workspace is JUnit Integration Stream Workspace.
3. If I right-click the above workspace --> Load, it shows me a different local folder, which is D:\workspace\sandbox
4. Which local folder is actually used during the build (assume there is a load action in the build script)? If every workspace already has a local folder, why need to define in build definition?



https://lh6.googleusercontent.com/-TfFx5oYkf0M/ThW89JtIe3I/AAAAAAAAEl4/YxXm-kUMsMU/s1440/build%252520local%252520folder.png

permanent link
Jirong Hu (1.5k9295258) | answered Jul 07 '11, 5:57 p.m.
Thanks for your reply. I am using RTC 3.

I think my question is: is every repository workspace has a local folder? Because when I create a new repository workspace, it asks for a local load folder. So if every repository workspace (include the one we created for build) already has a local folder, why asking in the build definition?

http://i54.tinypic.com/33ytllf.png

permanent link
Geoffrey Clemm (30.1k33035) | answered Jul 07 '11, 11:19 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Note that when you create a "repository workspace" on the server, the
repository workspace does not know where it will be loaded into the file
system (instead, the loaded files know which repository workspace they
are loaded from). That's a decision you make at "load time" (i.e. when
you load a repository workspace into the local file system). The RTC
plugins for Eclipse and Visual Studio keep track of where files have
been loaded in a given Eclipse or VS workspace (in the meta-data for
that Eclipse/VS workspace).

Cheers,
Geoff

On 7/7/2011 6:08 PM, hujirong wrote:
Thanks for your reply. I am using RTC 3.

I think my question is: is every repository workspace has a local
folder? Because when I create a new repository workspace, it asks for
a local load folder. So if every repository workspace (include the one
we created for build) already has a local folder, why asking in the
build definition?

http://i54.tinypic.com/33ytllf.png

Your answer


Register or 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.