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

Problems of using distributed build

Hi..
I am trying to execute builds in distributed machines. I used ant tasks (requestTeamBuild and waitForTeamBuild). I have some problems as follows:
1. How could I pass properties from the first build to the second one?
2. I want to add the second build log file to the first build. Is there any way I can do?
3. I don't understand the attributes deletePropertiesFile and overridePropertiesFile of requestTeamBuild task. Is there any one could explain how to use it?

Thank in advance.

Best Regards

0 votes



4 answers

Permanent link
Hi there,

1. How could I pass properties from the first build to the second one?

The requestTeamBuild task allows specifying an overridePropertiesFile containing properties to add or override.

For example, your script could do:
<echo "propA=value1" file="overrides.properties"/>

<echo "propB=value2" file="overrides.properties" append="true"/>
<teamRequestBuild ... overridePropertiesFile="overrides.properties"/>


2. I want to add the second build log file to the first build. Is there any way I can do?

Yes (we do this in our own integration builds). Use the above mechanism to pass the first build's UUID to the second build, then use that in the logPublisher task.

For example, in the first build's script:
<echo "parentBuildResultUUID=${buildResultUUID}" file="overrides.properties"/>

<teamRequestBuild ... overridePropertiesFile="overrides.properties"/>

then in the second build's script:
<logPublisher buildResultUUID="${parentBuildResultUUID}" .../>


3. I don't understand the attributes deletePropertiesFile and overridePropertiesFile of requestTeamBuild task. Is there any one could explain how to use it?

Hopefully this is clearer now from the examples above. See also the help topic linked above. The file format in both cases is the regular Java properties file format, with name=value, one per line.

1 vote


Permanent link
Since nested builds are not currently linked to each other automatically, I suggest doing this in your script using the linkPublisher task.

For example, from the child build, using the extra property from the example above, create bidirectional links with something like:

<linkPublisher buildResultUUID="${parentBuildResultUUID}" label="child build" url="${repositoryAddress}/resource/itemOid/com.ibm.team.build.BuildResult/${buildResultUUID}" .../>
<linkPublisher buildResultUUID="${buildResultUUID}" label="parent build" url="${repositoryAddress}/resource/itemOid/com.ibm.team.build.BuildResult/${parentBuildResultUUID}" .../>

0 votes


Permanent link
Hi.
Thank you. It is workable.
I have one more question about how to publish child build log to parenet build result. How can I get child build log file name when I used "<logPublisher>" in child build?


Best Regards

0 votes


Permanent link
I'm not sure I understand. Doesn't the child build determine the file name for the log? Can you give an example?

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
× 10,953

Question asked: Nov 11 '09, 4:46 a.m.

Question was seen: 6,135 times

Last updated: Nov 11 '09, 4:46 a.m.

Confirmation Cancel Confirm