Greetings!!!

Trying to create a CQ record automatically using BuildForge but was unsuccessful. Created the following environment variables

CQ_INTERACTION
CQ_DBNAME
CQ_USER
CQ_PASSWORD
CQ_DBSET
CQ_RELEASE_NAME

Assuming the CQ_INTERACTION=ON should trigger a perl script(bfcqbuild.pl) which is not happening. Ran the perl script from the command line and it worked perfectly fine and created a record.

Did anyone have the similar issue?

Appreciate your help.

Regards,

Raghu

Hi,

Did you get an error message? Also, were the CQ environment variables set in the environment group at the project level?

Brent Ulbricht
RTC Build Lead

Hello Brent,

Thank you for the reply.
Mentioned is the error i see in the log

sh: cqperl: not found.
Use of uninitialized value in pattern match (m//) at /PerlApp/BuildForge/Build/CQRecord.pm line 160.
Use of uninitialized value in scalar chomp at /PerlApp/BuildForge/Build/CQRecord.pm line 175.
Use of uninitialized value in pattern match (m//) at /PerlApp/BuildForge/Build/CQRecord.pm line 108.

and in the Management Console
10/20/11 09:49AM EXEC Build cancelled via Management Console.

I set the environment variable at the project level.

Found while browsing that it might be because of shebang line in the perl script. Hence changed the perl scripts (bfcqbuild.pl and bfcqresolve.pl) in the integration folder but of no use.

Thank You again,

Regards,

Raghu

Greetings!!!

Trying to create a CQ record automatically using BuildForge but was unsuccessful. Created the following environment variables

CQ_INTERACTION
CQ_DBNAME
CQ_USER
CQ_PASSWORD
CQ_DBSET
CQ_RELEASE_NAME

Assuming the CQ_INTERACTION=ON should trigger a perl script(bfcqbuild.pl) which is not happening. Ran the perl script from the command line and it worked perfectly fine and created a record.

Did anyone have the similar issue?

Appreciate your help.

Regards,

Raghu

Hi,

Did you get an error message? Also, were the CQ environment variables set in the environment group at the project level?

Brent Ulbricht
RTC Build Lead

We had the same problem in 7.1.2.1.

We checked the engine log and noticed that it was complaining that cqperl was not found. It didn't look in the default location that cqperl usually gets installed in.

So we added a symbolic link in /usr/bin/cqperl that points to /opt/rational/clearquest/bin/cqperl, which allowed the step to complete. (since /usr/bin/ was already in $PATH)

Thank You Chris,

That worked. The error is gone. But now i am facing a licensing issue. Mentioned below are the excerpts from the logs.

Thu Oct 27 09:18:22 CDT 2011: Build: 1814702: CRRBF0487I: CLEARQUEST: ERROR: The operation could not be completed because of a licensing error: License server system does not support this feature.

Thu Oct 27 09:18:22 CDT 2011: Build: 1814702: CRRBF0487I: CLEARQUEST: Feature: ClearQuest

Thu Oct 27 09:18:22 CDT 2011: Build: 1814702: CRRBF0487I: CLEARQUEST: For further information, refer to the FLEXnet Licensing End User Guide,

Thu Oct 27 09:18:22 CDT 2011: Build: 1814702: CRRBF0487I: CLEARQUEST: available at "www.macrovision.com".

Thu Oct 27 09:18:22 CDT 2011: Build: 1814702: CRRBF0487I: CLEARQUEST: Could not connect to ClearQuest - Invalid Initialization Data

Assuming to be fixed if we upgrade the licenses on the license server.

Thank You once again,

Regards,

Raghu

We had the same problem in 7.1.2.1.

We checked the engine log and noticed that it was complaining that cqperl was not found. It didn't look in the default location that cqperl usually gets installed in.

So we added a symbolic link in /usr/bin/cqperl that points to /opt/rational/clearquest/bin/cqperl, which allowed the step to complete. (since /usr/bin/ was already in $PATH)