runtimeverification / runtimeverification/kontrol
Improve CI by running kontrol build once
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Does it make sense to avoid running kontrol build on all four stages of Profiling (legacy) , Profiling (booster), Integration (legacy) and Integration (booster)?
Instead we could have a single stage of running kontrol build and copying the resulting out for each of the four stages.
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 by locating the CI configuration for the Profiling (legacy), Profiling (booster), Integration (legacy), and Integration (booster) stages, then inspect how each invokes kontrol build. Verify whether one build output can be copied into all four stages; done means the four stages reuse a single out result without changing their other checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100