Is there any way to build big projects with Bitbucket Pipelines?

[Alexander Nassian]

We are currently evaluating to switch to Bitbucket Pipelines (don‘t want wo self-host anything) but I‘m a little concerned about the limits.
We have builds with relatively big toolchains (Qt) and big build times and resources (Yocto). 200GiB disk space, 64GiB RAM, 16-32 Cores. Build times up to 10 hours.
Is there any way to force such builds into Pipelines (either with money or doing the actual build somewhere else like EC2)?

[Liam]

I am also looking I to this, did you find a solution?

I completely understand that BitBucket Pipelines (BBP), cannot handle a Yocto project directly, but I really want to associate the tickets from JIRA with a build attempt. If I cannot do that, then the value of the BB drops greatly.

The simple answer is to use SSH, but that will burn up BBP hours for no good reason. You can also hit the 1K minutes very easily.

Ideally I send the start build command from BBP, it puts the step in a working state, and I can report result/logs via an API.

[Alexander Nassian]

Yes, but unfortunately not with Bitbucket. We went for a own GitLab setup.

But what really drives me nuts is that you get super supported standard solutions for fancy kindergarden web stuff, but not for plain standard "execute build command a, b, c - boom binary" processes. That's not necessarily a BB problem but with many systems like that. As if real software went extinct with the trend to shitty websites that try to pretend they are real applications.

[upsampled]

I ended up keep my internal Bamboo instance and linking with JIRA Cloud. So far the App Link is only one way (Bamboo -> JIRA), but it is enough to associate the ticket numbers with the build. Also, though I have no idea how, Bamboo is reported builds to Bitbucket Cloud so I have a workable ecosystem right now.

As for everyone catering to web apps, yeah it's discouraging, but Yocto also takes way more horse power.