Skip to content

Update builder-playground usage for local devnet runs and testing#395

Merged
julio4 merged 1 commit intomainfrom
caner/update-builder-playground
Feb 23, 2026
Merged

Update builder-playground usage for local devnet runs and testing#395
julio4 merged 1 commit intomainfrom
caner/update-builder-playground

Conversation

@canercidam
Copy link
Member

📝 Summary

  • Using new playground.yaml for easy local devnet runs and testing in CI
  • Fixed builder-playground dir path detected by op-rbuilder when --builder.playground flag is used
  • Using new GitHub action for running builder-playground in CI and sending test tx
  • Simplified README

💡 Motivation and Context

builder-playground now supports unifying local and test run configurations under custom recipe files like playground.yaml and allows more simplicity in adding/overriding parameters. This PR brings the latest builder-playground experience for local devnet runs and introduces CI integration.


✅ I have completed the following steps:

  • Run make lint
  • Run make test
  • Added tests (if applicable)

Copy link
Contributor

@akundaz akundaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Is this meant to be for CI testing or for local usage? I always set the --block-time 1 arg when running builder playground and some other flashblocks related args on the builder

Copy link
Member

@julio4 julio4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks this looks great!

long = "builder.playground",
num_args = 0..=1,
default_missing_value = "$HOME/.playground/devnet/",
default_missing_value = "$HOME/.local/state/builder-playground/devnet",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we take into account $XDG_STATE_HOME? Maybe if not defined fallback to $HOME/.local/state in expand_path?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I thought the same but I was a little afraid of everyone having to do that. It's a small piece of complexity from the playground itself so maybe playground could tell it from builder-playground dir and we could rely on that here? (which should also allow a user to do cd $(builder-playground dir) easily.)

@julio4 julio4 merged commit f63a443 into main Feb 23, 2026
4 of 5 checks passed
@julio4 julio4 deleted the caner/update-builder-playground branch February 23, 2026 06:26
@julio4
Copy link
Member

julio4 commented Feb 23, 2026

We could potentially remove playground mod.

@canercidam
Copy link
Member Author

@akundaz The same setup in the recipe file supports both CI and local runs (and using for both in this PR). You could provide those flags from base_args in the recipe file!

Vui-Chee added a commit to okx/op-rbuilder that referenced this pull request Feb 24, 2026
…tokio-tar

* upstream/main:
  chore: rename bundle fields for consistency (no api change) (flashbots#402)
  Hotfix: pin nightly version to resolve str::as_str() regression (flashbots#401)
  update builder-playground usage for local devnet runs and testing (flashbots#395)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants