Conversation

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

Replying to

and

Well,

already needs to move to something like Jenkins using instances on a cloud provider like AWS, GCP, OVH, etc. directly. So I'd imagine the first step will be setting up CI, and then hooking up Gerrit to Jenkins isn't that hard.

Replying to

and

I’m actually not going to a cloud provider, I need predictable costs, so I’ll either selfhost or rent instances at fixed price.

Replying to

and

ovhcloud.com/en-ca/public-c is what I was thinking of in particular. The costs are quite predictable as long as you aren't scaling things up horizontally in an arbitrary way. Could go with persistent VPS / dedicated server if it's going to be churning away most of the time.

Replying to

and

I've been thinking about starting to use OVH public cloud instances for some development / testing builds. I certainly wouldn't try to use AWS because the pricing is ridiculous and they charge for bandwidth.

Replying to

and

A lot of the time I don't need more than my local workstation, but then sometimes I want to do a whole bunch of development builds and they really might as well be in parallel on separate instances. OVH pricing is really good and I think it could help me speed things up a lot.

Replying to

and

I can't really justify paying them for fancy dedicated servers to do development / testing builds because I'm just not going to use them enough. I was thinking about buying one and giving contributors SSH access to help contributors who don't have proper workstations though.

Replying to

and

32 core + 120GB memory compute instance with 400GB SSD and unlimited 10Gbps public bandwidth seems like it would work really well for doing a build. No clue which CPUs they give you for public cloud though. I'm used to their more traditional persistent VPS and dedicated servers.

Replying to

and

Pricing for Canada is $1.30 (CAD) / hour for the general purpose one and $1.94 / hour for the higher frequency CPU one. I'll probably try it out. I can't do release builds anywhere but locally but I could be doing some development/testing builds in parallel with those instances.

Replying to

and

I end up needing to do things like narrowing down which commit causes a problem where I need to do a ridiculous number of builds. It'd be so nice to have scripting to easily spin up a dozen of these and just end up paying something like 60 cents for each of the builds.

Replying to

and

Could also set it up so that a starting build can be uploaded when simply doing an incremental build. Sometimes I need to do many clean builds because I really need to rule out any possible problems and avoid false negatives / false positives for narrowing things down.

8:28 PM · Mar 20, 2021Twitter Web App