It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×1,192

question asked: Nov 29 '10, 4:30 p.m.
question was seen: 6,089 times
last updated: Jul 03 '13, 7:57 p.m.

Related questions

BuildForge 7.1.2 password suppress issues

0
Mike Ying (11●3●3) | asked Nov 29 '10, 4:30 p.m.
I have run into two cases related to password supression with BuildForge 7.1.2:

In both cases the setup has a standard variable named "ROOTPW" with "Assign Hidden" and "Suppress Display" in a global environment variable group, which gets included in all projects.

Case1: when I used a command line in a linked adapter execution block which uses the ${ROOTPW}, the BF7.1.2 console expands the command line and displays the password in clear text.

Case2: when I used the variable in a project step: c:\bybatch.bat ${ROOTPW} ${OtherParams}, BuildForge does not expand the variable and giving the message: "Variable expansion skipped: Hidden Variable (ROOTPW) detected". The result is that the literal ${ROOTPW} and ${OtherParams} gets passed to the batch file instead of the value of the variables ${ROOTPW} and ${OtherParams}.

All explaination, help and/or workaround are appreciated.

3 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Peter Birk (501●1●4●5) | answered Nov 29 '10, 7:29 p.m.
JAZZ DEVELOPER
Since you are on Windows, try specifying variables as %ROOTPW% instead of ${ROOTPW}. This will cause the variable to get expanded on the Agent with the correct syntax for BF variables on Windows.

Regards,
Peter Birk
BF/RTC Team Build Developer

I have run into two cases related to password supression with BuildForge 7.1.2:

In both cases the setup has a standard variable named "ROOTPW" with "Assign Hidden" and "Suppress Display" in a global environment variable group, which gets included in all projects.

Case1: when I used a command line in a linked adapter execution block which uses the ${ROOTPW}, the BF7.1.2 console expands the command line and displays the password in clear text.

Case2: when I used the variable in a project step: c:\bybatch.bat ${ROOTPW} ${OtherParams}, BuildForge does not expand the variable and giving the message: "Variable expansion skipped: Hidden Variable (ROOTPW) detected". The result is that the literal ${ROOTPW} and ${OtherParams} gets passed to the batch file instead of the value of the variables ${ROOTPW} and ${OtherParams}.

All explaination, help and/or workaround are appreciated.
0
permanent link
Mike Ying (11●3●3) | answered Dec 01 '10, 8:27 p.m.
Thanks Peter. It worked!

Since you are on Windows, try specifying variables as %ROOTPW% instead of ${ROOTPW}. This will cause the variable to get expanded on the Agent with the correct syntax for BF variables on Windows.

Regards,
Peter Birk
BF/RTC Team Build Developer

I have run into two cases related to password supression with BuildForge 7.1.2:

In both cases the setup has a standard variable named "ROOTPW" with "Assign Hidden" and "Suppress Display" in a global environment variable group, which gets included in all projects.

Case1: when I used a command line in a linked adapter execution block which uses the ${ROOTPW}, the BF7.1.2 console expands the command line and displays the password in clear text.

Case2: when I used the variable in a project step: c:\bybatch.bat ${ROOTPW} ${OtherParams}, BuildForge does not expand the variable and giving the message: "Variable expansion skipped: Hidden Variable (ROOTPW) detected". The result is that the literal ${ROOTPW} and ${OtherParams} gets passed to the batch file instead of the value of the variables ${ROOTPW} and ${OtherParams}.

All explaination, help and/or workaround are appreciated.
0
permanent link
praveen patidar (86●2●35●44) | answered Jul 03 '13, 7:57 p.m.
same issue happening with my Linux server. I am using Solaris box as build server and the RBF is as Build Forge Server.

Is there any work around for that?

Your answer

Register or to post your answer.


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.