WarpBuild

My life's goal is to make this obsolete - xkcd.com/303/

We're hiring. Links in QT

@awakecoding We've had too much abuse coming from personal accounts because of which we stopped supporting them.

@WarpBuilds Simply put, I just want to put in a credit card and try it on a few workflows that don't have anything confidential, but I'd rather not have to either try it on the real GitHub organization, and I don't really want to create a test GitHub organization

What's the simplest way to get Windows GitHub Actions runners that support Hyper-V? That's like the one thing I've always dreamed of, and I still can't find a way to do it without fixed hardware running 24/7 or dynamic VMs that need external orchestration and cleaning up

@awakecoding Not at this time.

@WarpBuilds do you support Windows runners with nested virtualization and Hyper-V enabled? I would really like to automate the creation of Hyper-V VMs in GitHub Actions, where the finished VHDX is uploaded somewhere at the end of the job

⏰ BuildJet is shutting down on 31st March. WarpBuild is the obvious choice to migrate to, because: 1. WarpBuild runners are faster for x86-64 and arm64 workloads. 2. WarpBuild has the broadest range of OSes and architectures supported (including Windows and MacOS) 3. WarpBuild has the most deployment modes , including Bring-Your-Own-Cloud on AWS, GCP, and Azure. Switch now for faster and cheaper builds. Here is the prompt you can provide to your favorite coding agent to make the switch: ``` Migrate runners from BuildJet to WarpBuild. The configuration for the WarpBuild runners can be found here: warpbuild.com/docs/ci/cloud-… ```

@suryaoruganti Here's a longer post about the migration: warpbuild.com/blog/buildjet-…

@suryaoruganti Get started with snapshot runners here: warpbuild.com/docs/ci/snapsh…

We are the only GitHub actions runner infrastructure provider to support this feature: Snapshots. Each CI job runs in its own ephemeral VM for isolation and reproducibility reasons. However, a significant portion of time in each job is spent on tasks that are repeated often. These are tasks like setting up dependencies, downloading artifacts that seldom change, etc. WarpBuild's snapshots capture the full state of the VM at any point in the job's lifecycle and use that as the base for subsequent jobs. This has enormous potential because it can even cache things like partial compilations, test suites, etc. with zero effort by users. One of our customers wrote a blog post about how they use WarpBuild snapshots in their CI to cut run times by 60-80% and save 24 minutes of CI time per commit. Truly grateful to have fantastic customers like Andrew Berry. Read his article here: ddev.com/blog/ddev-ci-w…

@tsybalab We support iOS SDK in MacOS runners.

@WarpBuilds I searching for iOS

2X faster GitHub actions runners, 50% cheaper for Linux, Windows, MacOS. No subscription required!

猛然发现自从用上了 @WarpBuilds 新的高配 CI Runner 以后，ScopeDB 的发布时间只需要十五分钟了。 配置单价翻一倍，耗时减少一半，四舍五入是 netwin，这就是 SaaS 的魅力（x） 此处应该惊出一身冷汗？

tldr: We provide github actions runner compute. Our compute is still cheaper than using github hosted runners (even with the $0.002/min tax) and our runners are optimized for high performance to minimize the number of mins consumed. Here are the practical implications and considerations to optimize for cost, given the new pricing. These are generic and ensure you think through your workflows and runners before making any changes. 1. Self-hosting runners is still cheaper than not Despite the $0.002/minute self-hosted runner tax, self-hosting runners on your cloud (aws/gcp/azure/...) remains the cheaper option. 2. Prefer larger runners If your workflow scales with the number of vCPUs, prefer larger runners. That ensures you spend fewer minutes on the runner, which reduces the GitHub self-hosted runner tax. For example, using actions-runner-controller with heavy jobs running on 1 vcpu runners is not a good idea. Instead, prefer a 2vcpu runner (say) if it runs the job ~2x faster. 3. Prefer faster runners All else being equal, prefer faster runners. That ensures you spend fewer minutes on the runner, which reduces the GitHub self-hosted runner tax. For example, if you're self-hosting on aws and using a t3g.medium runner, it's better to use a t4g.medium runner since the newer generation is faster, but not much more expensive. 4. Prefer fewer shards If you have a lot of shards for your jobs (example: tests on ~50 shards), consider reducing the number of shards and parallelizing the tests on fewer but larger runners. 5. Improve job performance This is not new advice, but it's now more important than ever because of the additional GitHub self-hosted runner tax. 6. Use GitHub hosted runners for very short jobs For linters and other very short jobs, it's better to use GitHub hosted runners.

Today, GitHub announced a change to their pricing model aimed at monetizing self-hosted runners. They've also reduced the pricing for their first party hosted runners. Here's what it means for our users: warpbuild.com/blog/github-ac…

@sebastiaanluca We had downtime earlier - warpbuild.instatus.com Following up over email.

@WarpBuilds Our runners aren't doing much atm: "Waiting for a runner to pick up this job..." or 503 error response. Sent some details via mail but not much in there.

《我看到屏幕上的好好好越来越多了》 @WarpBuilds Great experience!

Easy debugging for your GitHub actions jobs.

We've matured this with a lot of hard work and engineering first principles.

Responsiveness on the support channels is an underrated retention tactic.

@CFC_Busco We're hiring primarily for engineering at this time.

@WarpBuilds Hello, do you have an open role for the community?

We are hiring!

AWS us-east-1 region is facing a major outage. No WarpBuild services are affected. Our status page, marketing website and docs pages are on vercel though and those are down 😅

We're trying @WarpBuilds, and used their Docker builder. The results? The workflow that tests a web server utilizing Docker that would take 7-7.5 minutes without the builder takes 4.5 minutes with the WarpBuild's Docker builder! We can ship faster as a result!