Skipped by default configuration stage may be not so useful
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- build-system, cli
Research direction
Start with the incremental-builds documentation and the build command's configuration-stage handling. Determine how the existing command to rerun skipped configuration works and whether the requested control belongs globally or on the build command; done means the optimization can be disabled as described, with the default behavior and command-line usage documented.
Written by the indexing model from the issue text.
Description
By default BuildStream omits configuration steps on subsequent builds for optimization purposes (https://docs.buildstream.build/master/developing/workspaces.html#incremental-builds). There is a command to overcome that, but actually this optimization does not seem useful at least at the initial stages of development, e.g. when adding new elements and changing configuration frequently. For instance, I often spend much more time to understand problems and to run necessary missed configuration steps, then I get from this optimization.
It would be great to have an ability to disable this optimization either globally or for the build command. Probably, it has sense to disable it by default and to enable it, say, via an extra command-line argument.
- Dominant language
- Python
- Stars
- 144
- Forks
- 45
- Avg merge
- 20h 38m
- Merged PRs (30d)
- 6
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.
More from apache/buildstream
-
logging
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/buildstream#2150 · 3 comments ·
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
apache/buildstream#2143 · 2 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/buildstream#2194 ·
-
Modification time of an element with an open workspace propagates into consumer element's sandbox Openbug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
apache/buildstream#2186 · 2 comments · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/buildstream#2184 · 1 comment ·
All issues in apache/buildstream
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100