You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I wan to implement "runner" in Bitbucket and I have admin access on one of the bitbucket repo too but I am unable to see runner option in repository setting.
What could be the issue ?
How to check if runner option is activated or not in our account ?
or suggest how to get runner option in bitbucket.
Hi @manoj kumar,
I believe the reason may be that no other repo in that workspace has ever used Pipelines.
You can select the Pipelines option from the left sidebar when viewing the repo:
Then, create and commit a bitbucket-pipelines.yml file in the repo from that page, and afterwards you should be able to see the option to create a runner in the Repository settings.
Please keep in mind that if you don't use the following option in your bitbucket-pipelines.yml file's steps
and if the pipeline you define there is the default one or one running on the repo's main branch, then the first Pipelines build will run in our own infrastructure and consume the workspace's billing minutes.
If you don't want that, you can add the above definition for self-hosted in the steps, and then the first build will fail (since no runner will be available) without consuming build minutes.
Please feel free to let me know how it goes and if you need anything further.
Yes, this is correct. Pipelines and Pipelines Runners are only available for Bitbucket Cloud (repos hosted in https://bitbucket.org/) and not for Bitbucket Server or Data Center.
If you are using Bitbucket Server / Data Center, you can look into Bamboo. It is a CI/CD tool that you can integrate with your self-hosted instance.
If you are using self managed Bitbucket server then its not available, in the request you have mentioned Deployment type: CLOUD and TAGS: Bitbucket Cloud which confuse us earlier.
Unfortunately, you can't get this feature in self hosted Bitbucket Server/Datacenter product.