Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How do I set 8x step build on my bitbucket-pipelines.yml at the definitions part using slf hosted??


i tried to use this 8x feature on my bitbucke pipelines just putting size: 8x but it seems that it didn't use 32gb because my docker build does not run till the end. 

that build nowadays works in this way:


# Define the default Docker service with 2 GB memory limit
memory: 1024
# Define the Docker service which requires 6 GB memory
# You will have to define the service type if it is docker
type: docker
memory: 7168
- step:
name: Push
image: atlassian/pipelines-awscli
# Pass the Docker service with 7 GB
- docker-7g
but i would like to have the possibility os using more than 7gb if it would be possible as the bitbucket documentations says here:

Usage limits

The following are the usage limits or quotas applied to Bitbucket Pipelines Runners:

  • Step build time. Similar to Cloud, there is a maximum build time of 120 minutes per step. To reduce the total run time, we recommend using more parallel steps within your CI/CD workflow.

  • Max available memory. With Runners, you can configure up to 32GB (8x) of memory to run your builds.     "

that's the link:



1 answer

0 votes
Patrik S Atlassian Team Jun 14, 2022

Hello @Joao Moyses Moura Alves ,

Thank you for reaching out to Atlassian Community! 

The documentation you have linked is for Pipelines Runners, meaning that it is specific for the case where you run your build step in your own infrastructure. For steps that run in the Bitbucket infrastructure, you can only go up to 2x. For steps that use Runners and are executed in your own infrastructure, you can set to 2x, 4x, and 8x.

In this case, if you want more than 7GB for your docker service, you need to use Runners to run your build step.

First, you will need to create a runner either in your repository or workspace, and start it on your own infrastructure :

And then you will have to configure the steps you want to be executed in the runner by adding the runs-on keyword in the bitbucket-pipelines.yml file, like the below example : 

- step:
- 'self.hosted'
- 'my.custom.label'
size: 8x
- echo "This step will run on a self hosted runner with 32 GB of memory."


Hope that helps! Let me know in case you have any questions.

Thank you, @Joao Moyses Moura Alves .

Kind regards,

Patrik S

hey Patrik


I think i tried it but i might have done it wrongly. iĺl try it again and se what happens.



Like Patrik S likes this

Hey Patrik


Thatś what i was looking for.



Like Patrik S likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events