Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Add inputs to kurtosis-op workflow to override op-geth and op-node images [OPTION 2] #28

Merged
merged 8 commits into from
Jan 22, 2025

Conversation

janjakubnanista
Copy link
Collaborator

@janjakubnanista janjakubnanista commented Jan 22, 2025

Description

  • Adds a new local kurtosis job
    • Uses locally built op-node and op-geth images in kurtosis-op
    • The images are built from repositories provided when the workflow is dispatched and are not necessarily coming from the optimism and op-geth repos, a fork can be specified as a source. The repos are cloned and the requested ref is checked out dynamically
  • Preserves the original remote job

Since the repos are parametrized, one must be careful about them as they could potentially cause a security breach. Don't run this action with just any repo!

Fixes #14

@janjakubnanista janjakubnanista force-pushed the jan/workflow--002 branch 2 times, most recently from 19afd66 to a64f16e Compare January 22, 2025 03:04
Copy link
Member

@emhane emhane left a comment

Choose a reason for hiding this comment

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

if the op-reth image can be built from a local branch instead of being downloaded that would be better.

this is such a cool open-source contribution. for example @joshieDo sometimes has an op-node branch from his fork to test with op-reth. smthg interesting to upstream? or to odyssey maybe cc @onbjerg

.github/workflows/kurtosis-op.yml Outdated Show resolved Hide resolved
.github/workflows/kurtosis-op.yml Outdated Show resolved Hide resolved
.github/workflows/kurtosis-op.yml Outdated Show resolved Hide resolved
@janjakubnanista
Copy link
Collaborator Author

if the op-reth image can be built from a local branch instead of being downloaded that would be better.

this is such a cool open-source contribution. for example @joshieDo sometimes has an op-node branch from his fork to test with op-reth. smthg interesting to upstream? or to odyssey maybe cc @onbjerg

At the moment, all the images can be built off any git branch actually:

  • op-reth image is built by the workflow and depends on which branch you run the workflow on
  • op-geth repo & ref (branch/commit hash) depend on the workflow parameters, they have some reasonable defaults but can be changed to any fork/branch
  • op-node repo & ref (branch/commit hash) depend on the workflow parameters, they have some reasonable defaults but can be changed to any fork/branch
Screenshot 2025-01-22 at 7 34 36 AM

@janjakubnanista janjakubnanista merged commit b61f096 into optimism Jan 22, 2025
28 of 29 checks passed
@janjakubnanista janjakubnanista deleted the jan/workflow--002 branch January 22, 2025 16:59
@janjakubnanista janjakubnanista self-assigned this Jan 24, 2025
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.

L2-to-L1-message-passer op-node image for kurtosis-op
2 participants