self hosted pipelines still have a memory limit

[Rodrigo Orph]

Hello,

I finally got beta access to the self-hosted build pipelines, however, the memory allocation limits (8G for size 2x) still applies, and the yml schema doesn't allow us to change it.

Is there anyway to configure this limit?

The main reason why were are running this self-hosted is due memory constraints in the cloud solution.

Update:

Additionally, the pipeline seem to completely ignore `size` and `definitions` for docker memory limit, it always run a `build` instance limited to 1G ram (with and without explicit limits)

Thanks

[Caroline R]

Hi, @Rodrigo Orph! 

At the moment, self-hosted runners are targeting feature parity with cloud runners and this applies to memory allocation which is still limited to 4/8GB. This is something that the team will be looking into over the next weeks/month. You can find more info about these changes in this post: 

• Bitbucket Pipelines Runners is now in open beta

I hope this helps, but do let me know if you have any questions. 

Kind regards,
Caroline