ethereum-optimism / ethereum-optimism/optimism
ci: Use dynamic config with path-filtering to conditionally run CI jobs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 134
Description
CircleCI offers a dynamic config feature with a path-filtering orb that can be used to conditionally run parts of the CI depending on which files changed. We can use this to only run the Kona CI if files inside Kona changes. Same for some contracts tests.
The feature is documented [here](https://circleci.com/docs/guides/orchestrate/using-dynamic-configuration/#execute-specific-workflows-or-steps-based-on-which-files-are-modified).
This is a cleaner and faster method than the `check-changed` python script that we currently use.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing check-changed Python script and the CircleCI configuration, then read the linked dynamic-configuration and path-filtering documentation. Confirm how Kona files and contract-test files are detected today; done means those jobs run only when their relevant files change and the existing checks remain covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100