RTC Ant Attribute Questions

1) Yes, the personalBuild property will be set to true for personal builds.

2) I don't see any properties, but you might be able to accomplish that via the buildRequesterUserId property, if you are using a functional ID assigned to automated builds. Requested builds from users should not be done using a functional ID.

3) I don't think so, for your sake, let's home I'm wrong.

John Czukkermann
IBM Corp.
z/OS Management Facility Design and Development

For some reason, I don't see buildRequesterUserID or activityID being set with some echo statement in my Ant build.xml. PersonalBuild does get set though.



My RTC server is 3.0.1 but my local client is 3.0, it should work, shouldn't it?

 <echo>

        	Some Build Debugging info  

                The activityId is defined as ${activityId}

        	The buildRequesterUserId is ${buildRequesterUserId}

        	personalBuild is ${personalBuild}

 </echo>

and in the log I see

     [echo]         	Some Build Debugging info  

     [echo]          The activityId is defined as ${activityId}

     [echo]         	The buildRequesterUserId is ${buildRequesterUserId}

     [echo]         	personalBuild is true

For some reason, I don't see buildRequesterUserID or activityID being set with some echo statement in my Ant build.xml. PersonalBuild does get set though.



My RTC server is 3.0.1 but my local client is 3.0, it should work, shouldn't it?

 <echo>

        	Some Build Debugging info  

                The activityId is defined as ${activityId}

        	The buildRequesterUserId is ${buildRequesterUserId}

        	personalBuild is ${personalBuild}

 </echo>

and in the log I see

     [echo]         	Some Build Debugging info  

     [echo]          The activityId is defined as ${activityId}

     [echo]         	The buildRequesterUserId is ${buildRequesterUserId}

     [echo]         	personalBuild is true

AFAIK buildRequesterUserID is available only from RTC 3.0.1.

Have you tried from 3.0.1 client?