You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
G'day @Jason Legako
Based on your description you wish to use environment variables in your steps name?
If yes, that's an expected outcome because the name is supposed to be unique and used to describe the step. The environment variable is only available under Script, as it's used to specify a list of commands to be run.
I can't locate any existing Feature requests on this, so if you are interested, please let me know so I can raise one.
TYVM. I see, yeah raise a ticket imo, would be really important to be able to name which UI tests are running based on to/from branch.
So you're saying it HAS to be inside a script whereas the docs say it can be inside the file OR a script?
From the Docs: https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/
"You can access the variables from the bitbucket-pipelines.yml file or any script that you invoke by referring to them"
Hey @Jason Legako
Apologize for the confusion. The script I mention is in the YML configuration.
With that said, I have raised a new feature request on behalf of you at:
Don't forget to Vote and Watch the feature request so that you'll receive an update whenever we have any in the future.