Location of successful Build output through RTC Build Engine

We are integrating RTC with Build Forge.After successful running of build using RTC BUild Engine,at what location can we find .EAR file stored.OR there might be some end file which gets generated after successful build.What is that file and what is the location of it? Also if my assumption is wrong for EAR file, I would like to know what is the output of successful Build, Is it a JAR file or EAR file? I found one one link https://jazz.net/wiki/bin/view/Main/RationalBuildForge/CallingBuildToolkitAntTasksFromBuildForgeToFeedContributions#Final_Build_Result_Summary_Super , here it was mentioned that wee get the download option and we get binary JAR file but I didn't find the download option on my successful build. I got External Links which takes me to Build Forge Console.

Hi

I am not sure if I understand the question, so apologies in advance. Your build output will go to where your build scripts tell it to go. However, generally, the build output is stored relative to the local workspace where the files are copied from the repository workspace. Check your build definition to see where the local workspace is stored on your build machine(s).

anthony

Will it be a JAR file or EAR file?

Hi,

as Anthony wrote you write the build scripts and define what they do. They can create any type of output. Exe, zip, EAR, WAR, JAR,.....
Your build scripts can then publish the results to the build result using the available ANT tasks for the jazz buildsystem toolkit e.g. result publishing.

To keep the size of your database smaller I'd suggest to make the build scripts storing the results on a fileserver instead e.g. a directory containing the build uuid. You could publish only a link to that directory.

Please find more here http://jazz.net/projects/rational-team-concert/learnmore/ there is a section with links to more information on builds.

Ralph

Will it be a JAR file or EAR file?

Here's an example of what's been suggested.

The Build Forge agent will execute in a directory relative to the environment variable $BF_STEP_ROOT. Example: BF_STEP_ROOT=c:\temp\RTC_Integration_Project\BUILD_7.

It's likely you will fetch your build files, buld them and have a resulting WAR/JAR artifact somewhere below this directory. The next step during your build would be to publish the artifact. You can use the Build Toolkit Ant Tasks, referenced here to accomplish that.

http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.team.build.doc/topics/r_ant-tasks.html

Specifically, look at this task: http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.team.build.doc/topics/r_artifactfilepublisher.html.

Here's an example Ant script with target "publishJAR" which creates an activity (a note in the build result of what you are doing), JARs your compiled code, and then publishes the JAR file using the artifactFilePublisher Ant Task.

<target name="publishJAR">
<startBuildActivity repositoryAddress="${repositoryAddress}"
userId="${buildUser}"
password="${buildPassword}"
label="${buildActivityName}"
autoComplete="true"
verbose="true"
buildResultUUID="${buildUuid}" />

<jar jarfile="${basedir}/../application-${buildLabel}.jar">
<fileset dir="${basedir}/../bin">
<include name="**/*.class"/>
<exclude name="**/*samples/*.class"/>
</fileset>
</jar>

<artifactFilePublisher buildResultUUID="${buildUuid}"
repositoryAddress="${repositoryAddress}"
userId="${buildUser}"
password="${buildPassword}"
verbose="true"
filePath="${basedir}/../application-${buildLabel}.jar"
label="Application JAR" />
</target>

The Build Forge step for calling this Ant task might look like this:

call $ANT_HOME\bin\ant -verbose -lib "$team_scm_fetchDestination\releng\compiler\ecj.jar" -lib "$Build_Toolkit_Path" -f "$Ant_Script" -D"repositoryAddress"="$Repository_Address" -D"buildUuid"=$buildResultUuid -D"buildPassword"=$Build_Password -D"buildActivityName"="Build Forge Step #$BF_SID - $BF_STEPNAME" -D"buildStepId"="$BF_SID" -D"basedir"="$BF_ROOT" -D"buildLabel"="$BF_TAG" publishJAR


You may not need all of these variables in your script. Each -D variable is something needed by the Ant script. You have to decide what is necessary and what is not. The $Ant_Script will reference the file that contains the Ant target above.

Hopefully this helps.

Regards,
Pete