quickwit-oss / quickwit-oss/quickwit
Optimize the building of binaries/docker images.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
The build-ui step is just generating a bunch of static files that are be part of quickwit binary.
Currently, this build-ui step is executed when we build a docker image and when we build each binary. This means that we are repeating this build-ui several times.
We could have a first step job build-ui that uploads the artifacts and the subsequent jobs that downloads those artifacts.
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
Inspect the CI jobs responsible for the build-ui step, binary builds, and Docker image builds. Confirm where the generated static files are produced and how job artifacts can be passed to later jobs; done means build-ui runs once while all subsequent builds reuse its output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100