Skip to content

Conversation

@benjyw
Copy link
Contributor

@benjyw benjyw commented Jan 9, 2026

Depot have reached out about this, so I want to see how easy it is.

Depot have reached out about this, so I want to see how
easy it is.
@benjyw benjyw added the release-notes:not-required [CI] PR doesn't require mention in release notes label Jan 9, 2026
@benjyw
Copy link
Contributor Author

benjyw commented Jan 9, 2026

Nice! The Depot Linux x86 shards seem to be quite a bit faster than on GHA hardware. But I need to do a fully uncached build on both to verify apples-to-apples.

@cburroughs
Copy link
Contributor

👀 oh cool, is that a REAPI offering too? https://depot.dev/products/cache

@sureshjoshi
Copy link
Member

Oh damn, Depot coming in hot... A Pants client used them, and they were wayyy faster

@benjyw benjyw marked this pull request as ready for review January 26, 2026 01:50
@benjyw
Copy link
Contributor Author

benjyw commented Jan 26, 2026

We now have access to their macos runners, so this should all pass. Once this is in I will look at switching to them for Linux ARM as well, and to trying out their REAPI offering.

@cburroughs cburroughs mentioned this pull request Jan 28, 2026
9 tasks
@sureshjoshi
Copy link
Member

Is there a rough estimate on how much faster these are? The CI is tricky, since it sporadically uses cache.

Also, for running CI in forks, this would/should fail out of the box right? This is my ignorance related to how Depot was setup on the backend (e.g. is it whitelisted? Would this apply to scie-pants too?)

@benjyw
Copy link
Contributor Author

benjyw commented Jan 28, 2026

Is there a rough estimate on how much faster these are? The CI is tricky, since it sporadically uses cache.

Also, for running CI in forks, this would/should fail out of the box right? This is my ignorance related to how Depot was setup on the backend (e.g. is it whitelisted? Would this apply to scie-pants too?)

This PR was on a fork and it worked...

@sureshjoshi
Copy link
Member

Is there a rough estimate on how much faster these are? The CI is tricky, since it sporadically uses cache.
Also, for running CI in forks, this would/should fail out of the box right? This is my ignorance related to how Depot was setup on the backend (e.g. is it whitelisted? Would this apply to scie-pants too?)

This PR was on a fork and it worked...

It was a PR from your fork to pantsbuild/pants right?

I'm referring to running CI in the fork itself.

@benjyw
Copy link
Contributor Author

benjyw commented Jan 28, 2026

Ah, that would require a separate depot account for that fork I think.

So perhaps this should be switchable?

@sureshjoshi
Copy link
Member

Ah, that would require a separate depot account for that fork I think.

So perhaps this should be switchable?

Nahhh, no part of the Pants offering or documentation is making GHA in other forks work out of the box. It doesn't today anyways. I was just checking, as I have a patch that I can apply (or we can make the generate script handle this).

Not important as part of this PR.

@benjyw benjyw merged commit 541b606 into pantsbuild:main Jan 29, 2026
48 of 50 checks passed
@benjyw benjyw deleted the use_depot_runners branch January 29, 2026 03:55
@cburroughs
Copy link
Contributor

🚀 ! Excited to see these in action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-notes:not-required [CI] PR doesn't require mention in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants