[I] Skipped by default configuration stage may be not so useful [buildstream]

["eunovm (via GitHub)" <gi...@apache.org>]

eunovm opened a new issue, #2138:
URL: https://github.com/apache/buildstream/issues/2138

   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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Skipped by default configuration stage may be not so useful [buildstream]

["kotborealis (via GitHub)" <gi...@apache.org>]

kotborealis commented on issue #2138:
URL: https://github.com/apache/buildstream/issues/2138#issuecomment-4807550033

   I have some troubles with this too - sometimes I spend too much time debugging failing builds until i remember that I need to run `workspace reset --soft` to allow `configure-commands` step to run.
   
   >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.
   
   I don't think it would be possible to disable it by default, as it would be backwards-incompatible change. Maybe it could be opt-in, like via a parameter in `~/.config/buildstream.conf`?
   
   ```yaml
   # buildstream.conf
   ...
   disable-incremental-builds-optimization: true
   ...
   ```
   
   This way, users could disable this behaviour for their machine if they wish to.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org