IBM Support

PI29510: BUILD FORGE 8.0 ADAPTORS MATCH BLOCK DO NOT PARSE OUTPUT CORRECTUNDER MJC

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Under a Build Forge build using an adaptor, the command output
    is not parse using the regular expression in the <match> block.
    For example, the Build Forge build integrated with Rational Team
    Concert using the JazzJBE/JazzJBEv2 under the MJC (Java engine)
    fail to parse the "jbe" command return code output.
    
    247	11/6/14 2:21 PM		JIT	2014-11-06 19:21:14 [Jazz build engine]
    No requests found.
    248	11/6/14 2:21 PM		JIT	2014-11-06 19:21:14 [Jazz build engine]
    Exiting JBE after completing single build request, RC=1.
    249	11/6/14 2:21 PM		JIT	CRRTC3529W: The execution of Jazz Build
    Engine completed with a non-zero return code (RC=1).
    250	11/6/14 2:21 PM		JIT	ENDBFBomPlaceholder1415301669207
    251	11/6/14 2:21 PM		EXEC	end
    [/build/RTCBFbuild/BUILD_2@bfagent]
    252	11/6/14 2:21 PM		RESULT	0
    253	11/6/14 2:21 PM		INT	Finished Block Processing.
    
    Steps to reproduce:
    
    - Configured test adaptor "XXX" to run echo of the "jbe" failure
    output.
    
    ie:
    
    <?xml version="1.0"?>
    <!-- (c) Copyright by IBM Corp. and other(s) [2003], 2007 All
    Rights Reserved. -->
    <!DOCTYPE PROJECT_INTERFACE SYSTEM "interface.dtd">
    <PROJECT_INTERFACE IFTYPE="Source" INSTANCE="7.021">
    <interface>
    <run command="echo" params="" server="$BF_SERVER" dir="/"
    timeout="360"/>
    
            <ontempenv name="Failure" state="hastext">
    		<step result="FAIL" />
    	</ontempenv>
    </interface>
    	<command name="echo">
    		<execute>
    		echo "2014-10-31 13:43:47 [Jazz build engine] Exiting JBE
    after completing single build request, RC=1."
    		echo "CRRTC3529W: The execution of Jazz Build Engine completed
    with a non-zero return code (RC=1)."
    		</execute>
    	<resultsblock>
    		<match pattern="RC\=[0]">
    			<setenv name="Changes" value="TRUE" type="temp append\n" />
    		</match>
    		<match pattern="RC\=[1]">
    			<setenv name="Failure" value="TRUE" type="temp append\n" />
    		</match>
    		<match pattern="RC\=[2]">
    			<setenv name="Delete" value="TRUE" type="temp append\n" />
    		</match>
    	</resultsblock>
    	</command>
    </PROJECT_INTERFACE>
    
    - Created test project to run test adaptor via .source command.
    
    Expected result:
    
    The adaptor parses the output "RC=1" correctly and flags the
    build step to "FAILED" state.
    
    Actual result:
    
    The adaptor step does not parse the output "RC=1" and never
    flags the step.
    The adaptor step is then marked as "PASSED" by default.
    

Local fix

  • - Convert project to legacy Perl engine where issue is not seen.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of buildforge 8.0.0.x using an adaptor                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Under a Build Forge build using an adaptor, the command      *
    * output is not parse using the regular expression in the      *
    * <match> block.                                               *
    * For example, the Build Forge build integrated with Rational  *
    * Team Concert using the JazzJBE/JazzJBEv2 under the MJC (Java *
    * engine) fail to parse the "jbe" command return code output.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * upgrade to Build Forge 8.0.0.2-3-0066 to resolve the problem *
    ****************************************************************
    

Problem conclusion

  • Build Forge 8.0.0.2 ifix3 containing this fix. The new fix can
    parse the adaptor correctly
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI29510

  • Reported component name

    RATIONAL BUILDF

  • Reported component ID

    5724S2700

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-11-12

  • Closed date

    2015-03-25

  • Last modified date

    2015-03-25

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    RATIONAL BUILDF

  • Fixed component ID

    5724S2700

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSB2MV","label":"Rational Build Forge"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 October 2021