Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to configure jdk17 and maven version 4.1.0 in Bitbucket pipeline

sainath.emmadi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 22, 2024

Hi Team,

We are working on MuleSoft projects, as part of jdk version upgrade we are migrating from jdk8 to jdk17 with maven version is 4.1.0.

In this migration process, when i try to configure in the as bitbucket-pipeline.yml as below, Build is failing immediately. 

image: maven:4.1.0-jdk-17

 

Is there any solution/suggestion for this?

 

1 answer

1 vote
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 25, 2024

Hi Sainath and welcome to the community!

With the syntax you are using, Pipelines is going to look for the maven Docker image in DockerHub with the tag 4.1.0-jdk-17. However, an image with such a tag does not exist at the moment:

and I believe this is the reason that your build is failing.

You can find all available tags for the maven image here, and search by tag with the field "Filter Tags":

If you cannot find an existing Docker image with the version of maven and jdk you want, you can build your own custom Docker image and install on it the tools on the version you want. You can then push this image to DockerHub or another registry, and reference it in your bitbucket-pipelines.yml file. We support public and private Docker images including those hosted on Docker Hub, AWS, GCP, Azure and self-hosted registries accessible on the internet.

You can find more info on this page (at the end of the page there are resources on how to build your own custom Docker image):

Please feel free to reach out if you have any questions!

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events