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

Runners update: Support for Large Step Sizes, Custom Docker Images and Skip SSL on git clone

Hello everyone,

We are pleased to announce the release of a number of features today.
Please stop your runners and pull the latest image, the minimum version with support for these features is v1.179. To utilize these new features, the runs-on parameter must contain a 'self.hosted' label.

Large step sizes - you can now allocate additional memory to a step that runs on a self-hosted runner. Valid sizes are 1x, 2x, 4x, and 8x.

Custom docker image - you can now have more control over the docker-in-docker daemon by specifying a custom image for the docker service when running a step on a self-hosted runner.

Skip SSL on git clone - you can now disable SSL verification during the git clone and instead allow using a self-signed certificate.

For more details see Configure your runner in bitbucket pipelines.

Happy coding!



I am not sure why you would even have a "Large step sizes" option. If we are able to host our own runner image, why can we not simply use the behaviour containers use? Which is by default using all available memory/CPU unless specified otherwise.

Like Sarah Preston likes this
Raul Gomis Atlassian Team Aug 18, 2021

Hi @Sander Mol ,

Thanks for the feedback. We believe it is a good practice to still enforce limits to ensure predictability in your builds and detect performance / memory issues during your testing phases (as we do with our Altassian-hosted runners). Also, we support multiple runners per machine now: running multiple builds on the same machine could introduce flakiness and variance due to builds clashing each other competing for resources.

Having all said, if you are interested, we are happy to discuss your specific use case and get your feedback to see how we can keep improving Runners. Feel free to send us an email to:



Like Sarah Preston likes this
Laura Holton Community Leader Oct 04, 2021

Thanks for the release update @Vaish 🙌

Like Sarah Preston likes this


Log in or Sign up to comment

Atlassian Community Events