It's all about the answers!

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

×1,192

question asked: Aug 23 '11, 3:41 p.m.
question was seen: 4,144 times
last updated: Aug 23 '11, 3:41 p.m.

Related questions

Evalulating Conditional IF statement to true in v7.1.2.2

0
Richard Fishback (11●5●4) | asked Aug 23 '11, 3:41 p.m.
I am trying to get if ${PKG_ASAP_FOLDER}==Y to evaluate to true in version 7.1.2.2

I have PKG_ASAP_FOLDER environment variable defined in a Build Forge environment
Name Value
Yes Y
No N

I created a non-threaded Conditional step
Condition: if ${PKG_ASAP_FOLDER}==Y

I choose Yes from the PKG_ASAP_FOLDER dropdown

When I execute the job, I get
Result = Skipped for the Package ASAP folder step

with this in the log:
ENV PKG_ASAP_FOLDER=Y
COND The conditon on the step evaluated false, step will not be executed

We are upgrading from version 7.02 to version 7.1.2.2 and I see a lot has changed with the Conditional statements and I have obviously missed something, somewhere. Any help would be appreciated, especially examples.

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Brent Ulbricht (2.5k●1●1) | answered Aug 23 '11, 5:16 p.m.
JAZZ DEVELOPER
I am trying to get if ${PKG_ASAP_FOLDER}==Y to evaluate to true in version 7.1.2.2

I have PKG_ASAP_FOLDER environment variable defined in a Build Forge environment
Name Value
Yes Y
No N

I created a non-threaded Conditional step
Condition: if ${PKG_ASAP_FOLDER}==Y

I choose Yes from the PKG_ASAP_FOLDER dropdown

When I execute the job, I get
Result = Skipped for the Package ASAP folder step

with this in the log:
ENV PKG_ASAP_FOLDER=Y
COND The conditon on the step evaluated false, step will not be executed

We are upgrading from version 7.02 to version 7.1.2.2 and I see a lot has changed with the Conditional statements and I have obviously missed something, somewhere. Any help would be appreciated, especially examples.


Hi,

There are a couple of options you could use. The statement below will work, but there are others.

true(${PKG_ASAP_FOLDER} == Y)

If you search in the documentation on 'Condition functions', you can find all the other variations.

Brent Ulbricht
RTC Build Lead
0
permanent link
Richard Fishback (11●5●4) | answered Aug 24 '11, 1:57 p.m.
I am trying to get if ${PKG_ASAP_FOLDER}==Y to evaluate to true in version 7.1.2.2

I have PKG_ASAP_FOLDER environment variable defined in a Build Forge environment
Name Value
Yes Y
No N

I created a non-threaded Conditional step
Condition: if ${PKG_ASAP_FOLDER}==Y

I choose Yes from the PKG_ASAP_FOLDER dropdown

When I execute the job, I get
Result = Skipped for the Package ASAP folder step

with this in the log:
ENV PKG_ASAP_FOLDER=Y
COND The conditon on the step evaluated false, step will not be executed

We are upgrading from version 7.02 to version 7.1.2.2 and I see a lot has changed with the Conditional statements and I have obviously missed something, somewhere. Any help would be appreciated, especially examples.


Hi,

There are a couple of options you could use. The statement below will work, but there are others.

true(${PKG_ASAP_FOLDER} == Y)

If you search in the documentation on 'Condition functions', you can find all the other variations.

Brent Ulbricht
RTC Build Lead

Brent -

Your variation worked perfectly!

Thanks.

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.