Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is it possible to use variables in the artifacts section of a step in the pipelines.yml file?

We have a custom pipeline with a "Project" variable defined.   Using the variable works fine in the script section, but doesn't appear to work in the artifacts section.

- step: build-test-apprevision
name: Build, Test, Create App Revision
- bash ./gradlew :$Project:createAppRevision
- $Project/build/artifacts/$Project-apprevision


Am i doing something wrong or is this not possible?

3 answers

I just found this and we have the same issue. The env variables seem to be parsed in many other sections of the bitbucket-pipeline such as condition.changesets.includePaths, but not in artifacts...

Tried to work with repository variables in condition.changesets.includePaths and it does not seem to work. Same thing with artifacts, of course.

It's really sad...

I encountered the same problem. I need to add a time-stamp to the artifacts name and it seems that variable references are not working in the "artifacts"-section. It would be good to know wether we are doing something wrong or if this feature will be added in near future. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events