I have different images based on environment, hence i want to use custom image in services, but implementation of any of the below throws error.
definitions:
services:
frontend:
image:
name: $docker_image
OR
services:
- $docker_image
Hi,
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
G'day, @Mohan Kona
Currently Bitbucket Pipelines doesn't support the usage of variables for step attributes, such as defining the image name. We do have a close feature request on this issue at:
Essentially, this feature request was close due to a new feature request release Dynamic pipeline. One of the MANY things Dynamic Pipelines solves is the ability to specific Docker image names via variables in Pipelines. Please check the documentation for more information:
https://support.atlassian.com/bitbucket-cloud/docs/dynamic-pipelines/
Regards,
Syahrul
Hi,
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.