Bitbucket runner

[gentian fb]

Dears ,

I have configure a bitbucket runner and implemented into the pipeline :

- step:

script:

- echo "Script under default section"

branches:

develop:

- step:

runs-on:

- self.hosted

- linux

script:

- echo "This script runs only on commit to the master branch"

- apt-get update

- apt-get install ssh

- scp * user@1.2.3.4:/home/

- ssh user@1.2.3.4 "cd /home/ && sudo docker-compose down"

The pipeline is working fine . I just want to know the idea behind the bitbucket runner. It does the build of the bitbucket process ,or create artifacts , in a remote instance without consuming bitbucket cloud ? If the runner create artifacts , is the runner who sends them to other instances ,or is the bitbucket cloud who does ?

Regards,

[Theodora Boudale]

Hi @gentian fb,

Steps that are configured to run on a runner run on your own infrastructure, on your own server, and you don't get charged for any Pipelines build minutes. Steps that are not configured to run on a runner will run on Atlassian infrastructure. There is a limit on the number of minutes you can use per billing cycle in this case, depending on the billing plan of your workspace, and if you want to use more you will get charged for extra minutes (with Runners you don't get charged for build minutes).

You can also use more memory for builds than run with runners, see here:

• https://support.atlassian.com/bitbucket-cloud/docs/configure-your-runner-in-bitbucket-pipelines-yml/#Large-step-size

For builds that run on our own infrastructure you can use up to 8 GB memory (with size: 2x). However, with runners, you can configure up to size: 8x for a step, with will give 32 GB of memory. This is useful if your builds need more than 8 GB of memory.

If you define in your bitbucket-pipelines.yml file artifacts for one step (like in the doc here: https://support.atlassian.com/bitbucket-cloud/docs/use-artifacts-in-steps/), these will be uploaded to Atlassian infrastructure even with runners. Steps from the same pipeline can be scheduled on multiple runners that run on different hosts. So in order to share caches and artifacts between steps we upload them to the Atlassian infrastructure.

Please feel free to let me know if you have any other questions!

Kind regards,
Theodora