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

[Steve Maxwell]

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
script:
- bash ./gradlew :$Project:createAppRevision
artifacts:
- $Project/build/artifacts/$Project-apprevision

Am i doing something wrong or is this not possible?

[Andrew Hill]

bitbucket suggests, in a completely non-patronising way, the use of premium dynamic pipelines to solve this

BCLOUD-21666 

"We're extremely excited to announce the GA release of a really powerful feature in Bitbucket Pipelines called Dynamic Pipelines. ......

One of the MANY things Dynamic Pipelines solves is the ability to inject variables into things like artefacts etc."

[Ruggero Schirinzi]

following @Felipe Jaekel  issue, the only way I found to handle this behavior is to specify into the artifacts section something like "*.json" and then to recalculate the filename in each following steps. It is tricky and clunky but it could works.

[david_treblig]

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...

[Fotis Papadamis]

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...

[Felipe Jaekel]

https://jira.atlassian.com/browse/BCLOUD-21666

[Marvin Kraner]

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.