You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Can you please update online documentation with CPU information regarding bitbucket pipelines? It currently says it has a 4GB RAM and 5GB space limit but no info about CPUs. Please provide some information about CPUs - count, relative power, shared/dedicated, etc.
The CPU specifications within Bitbucket pipelines is not a set CPU Core, Type or Speed. This is due to Bitbucket pipelines being ran using shared infrastructure. There is a feature request similar to your request (the feature request is more interested in constant performance, but it will explain more about the resources available). You may find the request at #13079: Provide a fairly constant CPU and network resource.
There are also recent changes to Bitbucket pipelines which can be located at Infrastructure changes in Bitbucket Pipelines. Within that document, back in August 2018 there was a infrastructure change to EC2 M5d which is listed within Amazon as 2-96 vCPUs and a CPU of Intel® Xeon® Platinum 8175M. You may find the amazon specifications at https://aws.amazon.com/blogs/aws/ec2-instance-update-m5-instances-with-local-nvme-storage-m5d/
I hope this helps to clarify which resources are available within Bitbucket pipelines.
In all cases, even in `self.hosted` runners, the CPU is limited to 4 cores. Even if you have 52 cores on your machine, you are done. This is how the CPU is set for Bitbucket Pipelines.
We wasted a lot of time designing and building pipelines, now for nothing. For all readers, I suggest you not use Bitbucket Pipelines.
P.S.: Atlassian keeps these 4 CPU limitation secret, just for you. ;-)