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?
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."
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.