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

[Deleted user]

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:

definitions:

services:

# Define the default Docker service with 2 GB memory limit

docker:

memory: 1024

# Define the Docker service which requires 6 GB memory

docker-7g:

# You will have to define the service type if it is docker

type: docker

memory: 7168

pipelines:

custom:

sandbox:

- step:

name: Push

image: atlassian/pipelines-awscli

# Pass the Docker service with 7 GB

services:

- 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:  https://support.atlassian.com/bitbucket-cloud/docs/runners/

[Patrik S]

Hello @[deleted] ,

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 :

• https://support.atlassian.com/bitbucket-cloud/docs/adding-a-new-runner-in-bitbucket/

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 : 

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

Reference: https://support.atlassian.com/bitbucket-cloud/docs/configure-your-runner-in-bitbucket-pipelines-yml/

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

Thank you, @[deleted] .

Kind regards,

Patrik S

[Deleted user]

hey Patrik

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

Thanks

[Deleted user]

Hey Patrik

Thatś what i was looking for.

Thanks.

[Bitwise DEVS]

For steps that run in the Bitbucket infrastructure, you can only go up to 2x.

@Patrik S is this still true to this day? Just read this and it seems we can now use 4x and 8x in Bitbucket Pipeline cloud?

[Patrik S]

Hello @Bitwise DEVS ,

Bitbucket Cloud recently announced the addition of 4x and 8x for builds that use Atlassian infrastructure. You can check more details in the following blog post : 

• Announcing our new CI/CD runtime, with up to 8x faster builds 

Please be aware that the new Pipelines size options are only available for builds running under a paid Bitbucket Cloud plan (Standard or Premium).

Thank you, @Bitwise DEVS !

Patrik S