7.1.1.x CQ integration on UNIX/Linux - errors

Chris,

* Is the CQ client working as expected?
* Can you run cqperl?
* Do you see any more information with BFCQDEBUG enabled?
* Alternatively as the BF console OS user, can you run /opt/rational/clearquest/bin/cqperl <BF>/integration/bfcqbuild.pl script you can just setup your shell with the same environment variables via export/set to emulate what is going on in BF?

So something like this, with the environment variables with default to a submit.
/opt/rational/clearquest/bin/cqperl /opt/buildforge/integration/bfcqbuild.pl

The most common issue I have seem is more of a generic one where there is s PERL5LIB var set that breaks cqperl so definitely give that a look, but give these suggestions a try and post your results.

-Sean

Sean,
Thanks for the reply ...
Yes, our CQ client and cqperl works
We don't have PERL5LIB set.

I had tried a couple different fixes, our original error in this thread was with a Build Forge environment variable: CQ_INTERACTION=ON, something I seen elsewhere in devWorks, but not in the IBM whitepaper.

I removed that var and the BF project step will now pass, but the BF_RECORD is never set, nor is a CQ BTrecord created in ClearQuest.

Might there need to be an adaptor set up?

-Chris

Yeah unfortunately the change in behavior that requires the new CQ_INTERACTION piece came after the whitepaper but has made it into the latest documentation.
http://publib.boulder.ibm.com/infocenter/bldforge/v7r1m2/index.jsp?topic=/com.ibm.rational.buildforge.doc/topics/adaptor_clearquest_build_records.html

Once that is enabled, you *should* be atleast calling the bfcqbuild.pl script to generate the BTBuild records, but if you are still not seeing the BF_CQ_RECORD_ID variable get created there may still be a problem where the engine is not triggering the call.

As for any additional debugging, you might want to try the standalone call via the shell, I was able to test that by setting up the env and a few variables that BF normally would provide, this will atleast validate that the script will work when it is called, then it is just a matter of figuring out why BF is not calling it.

Here is a version I just tried on Windows to verify:
http://pastebin.com/YzXgByVt

-Sean

Thanks Sean,
Following the instructions in the link, the project fails with:
1 01/25/11 01:07PM STEP Step using selector 'testserver'.
2 01/25/11 01:07PM EXEC Build cancelled via Management Console.

So I tried running `cqperl bfcqbuild.pl` from the command line, it's not liking my %ENV:

/opt/rational/clearquest/bin/cqperl ./bfcqbuild.pl
ERROR: The required environment parameter for operation was not set at ./bfcqbuild.pl line 267.

Could not connect to ClearQuest - Invalid Initialization Data

$ export CQ_DBNAME=ProdT
$ /opt/rational/clearquest/bin/cqperl ./bfcqbuild.pl
ERROR: The required environment parameter for operation was not set at ./bfcqbuild.pl line 267.

Could not connect to ClearQuest - Invalid Initialization Data
env | grep DBNAME
CQ_DBNAME=ProdT

thanks,
Chris

Actually, I had some success, I was setting the vars as myself and running bfcqbuild.pl with sudo. When I run bfcqbuild.pl as myself I get passed that.

DEBUG: DBSET:BFSchema
DEBUG: Curstate Is:
DEBUG: Reqstate Now: Submit
LOG: Release Record Created:
TEST_BASE_BF_CQ_INT
Parentheses missing around "my" list at (eval 1) line 518.
Parentheses missing around "my" list at (eval 1) line 519.
Useless use of a variable in void context at (eval 1) line 518.
Useless use of a variable in void context at (eval 1) line 518.
Useless use of a variable in void context at (eval 1) line 518.
Useless use of a variable in void context at (eval 1) line 518.
Useless use of a variable in void context at (eval 1) line 519.
Useless use of a variable in void context at (eval 1) line 519.
Useless use of a variable in void context at (eval 1) line 519.
Useless use of a variable in void context at (eval 1) line 519.
"my" variable $my_id masks earlier declaration in same scope at (eval 1) line 1205.
"my" variable $my_id masks earlier declaration in same scope at (eval 1) line 1395.
Possible unintended interpolation of @owner in string at (eval 1) line 1528.
ERROR: Failed condition: GetState() == AD_VALIDATED
Location: ClearQuest Core:adeditaction.cpp:742
GetState()=PREPARED at /apps/rational/clearquest/linux_x86/shlib/CQPerlExt.pm line 52.

Could not submit build record to ClearQuest

Chris,

Can you submit them directly in your CQ client on Linux ? Try with the same value you set in the environment vars to ensure they are valid lengths.
Also jic did you change the records or code that the packages added ?

-Sean

Yes, I am able to log into CQ and submit a BTBuild record :)
and no, we did not modify any CQ or BF code/packages :(

thanks,
Chris

Chris,

Well those were the low hanging fruit, what I would suggest next is to setup CQ tracing to at least see what is being set in CQ and why we are failing with an validation error, you can set these environment variables on the cli before running the script and post your output.

$ export CQ_DIAG_TRACE="API;HOOKS=2;PERL;THROW"  

$ export CQ_DIAG_REPORT="MESSAGE_INFO=0xffff;DIAG_FLAGS=-1"

$ export CQ_DIAG_OUTPUT=~/cq_trace.log

$ cqperl bfcqbuild.pl

Or modify the bfcqbuild.pl script to add output statements, namely around Commit to first perform a Validate and view the output with print statements.

-Sean

The problem was found to be that the bfcqbuild.pl has a 'cqperl interpreter' of "#!/usr/bin/cqperl".

I resovled it by softlinking /usr/bin/cqperl to /opt/rational/clearquest/bin/cqperl.

I'm thinking the default install location for cqperl is usually in /opt/rational/clearquest/bin, so Build Forge should expect it there.

Perhaps during Build Forge installation, the install should ask "If integrating with ClearQuest, where is cqperl located?"; like it does for the other dependencies like database files.

thanks,

You should file a defect for that if you have not already, in the least to document the issue.

-Sean