nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possile to use environment variables as image name for bitbucket pipelines?

Aleksei Terentev

Hello,

I was trying to set docker image name in `bitbucket-pipelines.yml` as a value of environment variable. Unfortunately, both ways I've tried failed:

step:
  image: $IMAGE_NAME

and

step:
  image:
    name: $IMAGE_NAME

If I replace $IMAGE_NAME with actual value - everything works fine.

Could you please tell me if there is a way to perform it?

Thank you,

Accepted answers

unknown

I have the same problem, seems like image name accepts only hardcoded values.

Caterina Curti

Hi all,

I've just published an article and a video showing how you can use a variable as the image name.

This solution is based on Dynamic Pipelines and requires a Forge app.

The article shows how to replace an "IMAGE_TAG" value (image: node:$IMAGE_TAG) but would work with no changes when the variable contains the full name of the image.

Hope this helps,
Caterina

All comments

Danyal Iqbal

Where did you set the variable?

Aleksei Terentev

I set it in team variables also tried local project variables.

unknown

I have the same problem, seems like image name accepts only hardcoded values.

Erik van der Valk

I can confirm that this isn't supported. I've tried several ways of defining the variable but all failed. Repository specific or team wide account variables aren't supported in the image name.

I'd love to see support for this!

Alex Tran_3tfku5

Would love to have this feature supported !

Marco Röhrs

would be awesome. I just stumpled upon this issue. removed all hardcoded values from my pipeline definition and added them to team-variables so they can be changed easily without having to change bitbucket-pipeline.yml in all repositories. for everything else it works so far, just image cant be substituted.

nickjj

I have the same issue.

It throws this error when using environment variables: There is a problem with the format of your docker image name at [image > name].

But if you goto the online validator it says it's syntactically valid with the environment variable.

My use case is that I'd like to define my AWS account id and region as environment variables so that the pipeline script is more portable between my local test BB account and the "real" repo.

Erik van der Valk

The problem with the validator is that it only checks the YAML syntax. Seeing as an image name should be a string, and either `my-image:latest` or `$MY_IMAGE` is considered a string, the validator checks out. However as you already understand it doesn't interpolate variables on that specific location.

Marco Röhrs

"I'd love to see support for this!" yes, please

golaod

I have the same issue with image name, but also with max-time. For the latter, it says that value should be integer and got string.

Rajan Paneru

Hoping to get this feature.

Denis Kalgushkin

I also hope to get this one day. We regularly upgrade gradle version in gradle.properties and in Jenkins we have the first step extracting gradle version from this file and then uses it for the next step so we don't need to touch pipeline file every time we upgrade gradle.

Elgiz Abbasov

How is this still not supported after almost 3 years?

unknown

So many use cases for this functionality! Please vote for this Feature Request: https://jira.atlassian.com/browse/BCLOUD-13014

unknown

Been waiting for 5 years now https://jira.atlassian.com/browse/BCLOUD-13014

Vote on it please!

Caterina Curti

Hi all,

I've just published an article and a video showing how you can use a variable as the image name.

This solution is based on Dynamic Pipelines and requires a Forge app.

The article shows how to replace an "IMAGE_TAG" value (image: node:$IMAGE_TAG) but would work with no changes when the variable contains the full name of the image.

Hope this helps,
Caterina

Gull Shair Butt

Are you kidding me, this is such a simple feature. And you are asking to upgrade to premium plan to use the Dynamic Pipeline using Forge mumbo jumbo. It's crazy..

Man, this is a simple feature available all over the places. You guys don't want anyone to stay here.

Peter_gcfuso

this should be supported natively without having to resort to dynamic pipelines (and thus a paid subscription).

This is basic functionality.

Sergey Mokhov

I'm on a paid subscription and do not want to deal with complexity of dynamic pipelines. I'd have to create and maintain a repository to host the code of the forge app, just so I can configure pipeline for another repository.

My use case is build a pipe image and test the pipe on a feature branch before I can merge it to master.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines

environment-variable