(r2) PostBuildandJenkins < Deployment

Engineering Lifecycle Management Wiki - Deployment

Community information and contribution guidelines

~~EditAttach~~Printable

TWiki > Deployment Web > DeploymentTroubleshooting > IntegrationsTroubleshooting > JenkinsAndHudson > PostBuildandJenkins

Revision 2 - 2013-11-26 - 20:59:17 - Main.zeech

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/new.png" alt="new.png" width="50" height="50" align="right"/> When selecting Post Build activities in the Build definition , after the build is complete no Post Build activities are triggered.
%DKGRAY% Authors: IntegrationsTroubleshootingTeam <br>
Build basis: Rational Team Concert 4.x 
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

---++ Subsequent analysis steps.
   
   * You need to invoke the Jazz ant participant com.ibm.team.build.autoDeliver in build.xml in a target after all the necessary build targets are completed.
   * The Jazz Build Engine participant step should be invoked from the Ant script using an EXEC block, so it will be able to access the variables necessary for the build. 

Example command :

<verbatim>
<target name="PostBuildDeliver">
	  <exec executable="cmd">
	    <arg value="/c"/>
	    <arg value="C:\PathToBuildToolKit\jazz\buildsystem\buildengine\eclipse\jbe.exe -userId $Build_User -pass $Build_pass -repository https://<host>:9443/ccm -buildResultUUID $buildResultUUID -engineId $engineId -participants com.ibm.team.build.autoDeliver -noComplete -verbose"/>
	  </exec>
	</target>
</verbatim>

Use case Example: if you are using the sample provided in [[https://jazz.net/wiki/bin/view/Main/JazzScmWithJenkins][Integrating with Jazz SCM and Builds from Hudson and Jenkins]] you need to modify buildOnHudsonJenkinsAdvanced.xml to invoke the participant _autoDeliver_

<verbatim>
	     <!-- Redirecting the output of the executable in the jbe_output2.txt -->
            <exec executable="${jbePath}/jbe.exe" output="jbe_output2.txt">
            <arg value="-repository"/>
            <arg value="${repositoryAddress}"/>
            <arg value="-userId"/>
            <arg value="${userId}"/>
            <arg value="-passwordFile"/>
            <arg value="${passwordFile}"/>
            <arg value="-buildResultUUID"/>
            <arg value="${buildResultID}"/>
            <arg value="-engineId"/>
            <arg value="${buildEngineId}"/>
            <arg value="-participants"/>
            <arg value="com.ibm.team.build.autoDeliver"/>  <!-- Run only the SCM phase -->
	    	 <arg value="-noComplete"/>  <!-- Don't complete the build until the main build script has run -->
            <arg value="-verbose"/>
            <arg value="-data"/>
            <arg value="/tmp/jbe-workspace-${buildEngineId}"/>  <!-- location for JBE's Eclipse workspace (not the loaded SCM workspace) -->
        </exec>
</verbatim>

Note: This participant does not get invoked when you define the Post Build activities in the Build definition. This needs to be invoked in a target for Post Build to work in RTC.


---+++++!! Related topics:

   * Still need help troubleshooting your integrations issue?  Refer to [[IntegrationsTroubleshooting][Integrations troubleshooting]] for additional topics.

---+++++!! External links:

---+++++!! Additional contributors: Main.ZeeshanChoudhry

---+++++!! Questions and comments:

%COMMENT{type="below" target="BuildForgeAndRationalTeamConcertPerformanceTroubleshootingComments" button="Submit"}%

%INCLUDE{"BuildForgeAndRationalTeamConcertPerformanceTroubleshootingComments"}%

Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
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.