Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Build warnings parser using variable in configuration

"Variables can be used to make values available when building plans in Bamboo."

 

I created a new variable called "warning.num" and tried to use this in the Build parser configuration in the field: Fail build threshold.

 

However, I've got: "Fail build threshold must be a number."

 

Is it possible to use a variable in that task field?

 

Thanks

 

1 answer

I'm assuming that you're using

$bamboo.warning.num

in the entry, and not just

warning.num

?

Under default plan configuration -> variables I've added:

trunk.warnings.num  with value 2

 

Then in build warnings parser I set the threshold to:

${trunk.warnings.num}

or 

${bamboo.trunk.warnings.num}

or 

$bamboo.trunk.warnings.num

 

All the time I get: Fail build threshold must be a number.

Maybe that field can't bet set as a variable?  It's also possible that the value is being parsed as the literal string "2", in which case that won't work either.  Hrm.  I've never used the Build Warnings Task, though.

I'd recommend opening a support ticket with Atlassian, then.

Like IG likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events