ci: move to buildjet

[kayagokalp]

Description

Moves CI runners to buildjet from github.

Benchmarks

	before	after
total	6823	4815
slowest	1004	717

Overall, %30 faster CI times, ~5 minutes removed for each PR in slowest run (e2e testing).

[IGI-111]

As I recall, we kept the standard runners on because the buildjet ones are more expensive. I think we should have a discussion about cost here.

[kayagokalp]

As I recall, we kept the standard runners on because the buildjet ones are more expensive. I think we should have a discussion about cost here.

Sure, the calculation below was my reasoning of opening this PR:

As far as I can see, buildjet runner I used here costs $0.008 / min

And cheapest x86 github runner is also $0.008/min.

That being said I think we have some CI minutes included in our github enterprise subscription, so not sure which makes more sense taking that account

cc @Voxelot

[byucesoy]

Hey folks,

Sorry for jumping in, but I saw this thread and wanted to chime in. Did you see Ubicloud runners? They are fully compatible with Github runners and 10x cheaper. You can for example pick a bigger runner, which would be faster (if the bottleneck is on CPU, memory or disk IO) and cheaper at the same time.

Disclaimer: I'm Ubicloud employee. Feel free to ask any questions you might have.

[sdankel]

🚀

[Voxelot]

The buildjet to github runner price comparison isn't apples to apples. While the prices are the same at the low tier, the buildjet runner is 2x the machine. On the whole build-jet is at least 2x cheaper than github when comparing similar runner specs.

We have a lot of minutes included in the enterprise plan, but those are only for the 2-core runners. I value the productivity of the team's CI cycles more than getting freebie minutes on slow machines.