Hi @Waqas shoukat and welcome to the community!
If your Pipelines builds run on Atlassian's infrastructure or on a Linux Docker self-hosted runner, these builds use Docker containers. For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file. So, the version of gradle that you see may be the one preinstalled on that Docker image you specify (unless you are installing gradle during the build).
If you are using a public Docker image as a build container, you can check any newer tags of this image and see if any image with a newer tag has a newer version of gradle.
If you have Docker installed on your computer, you can check that by running the command
docker run -it --entrypoint=/bin/bash atlassian/default-image:4
where atlassian/default-image:4 replace with the Docker image you want to check. The entrypoint in the command may need to be /bin/sh instead of /bin/bash depending on the image, but you can try /bin/bash first and if it doesn't work you can then try /bin/sh.
This command will start a Docker container based on this image and a bash prompt when the container starts. In the bash prompt of the container, you can run gradle --version to see what version of gradle is installed on that specific Docker image. You can repeat the process for multiple images and/or tags to see what version of gradle they have until you find a suitable one. For example, you can see different tags of the official gradle image here:
As I mentioned, the above applies to builds that run on Atlassian's infrastructure or a Linux Docker self-hosted runner. If you are using a Linux Shell, MacOS, or Windows runner, these builds run directly on the host machine so gradle probably needs to be updated there.
Please feel free to reach out if you have any questions.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.