On Tue, 5 May 2026 at 18:17, Trevor Gamblin <[email protected]> wrote: > > 2. Nomenclature: > > > > - "step" is a single command that is also given a short name and a > > longer description. Steps are building blocks for pipelines and can't > > be individually executed. > Why not? Why not have the ability to run something like 'bitbake-setup > run-step <step_name'? That would actually be an advantage this feature > could provide over many other CI systems, as it's usually difficult or > impossible to rerun individual steps (you have to re-run a whole job or > pipeline). I can see this being very useful for example when you need to > run 'bitbake -c testimage' in a loop many times to try and catch > intermittent failures.
The reason I suggested that steps can't be run individually is that I wanted to keep the UI simple, and couldn't think of use cases for individual steps. One has to start somewhere, my starting point is baffled yocto newcomers, and poorly written custom build scripts :) Anyway! This was very useful to read, and I agree with what you say. Here's how the UI could look like: 1. Interactively choose a pipeline and run it: $ bitbake-setup build 2. Run a pipeline given on command line: $ bitbake-setup build <pipeline-name> 3. List pipeline steps $ bitbake-setup build --list-steps <pipeline-name> (this can be used to avoid hardcoding step names and their sequence into CI-specific definitions, e.g. CI would first list the steps, then iterate over them, avoiding the 'giant single step' problem - this of course requires support for creating steps 'on the fly', which I think at least buildbot can do) 4. Run a single step: $ bitbake-setup build <pipeline-name> <step-name> 5. Run a pipeline, starting at a particular step: $ bitbake-setup build <pipeline-name> --start-at <step-name> 6. Run a pipeline, stopping after a particular step: $ bitbake-setup build <pipeline-name> --stop-after <step-name> Etc. How's this looking? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2326): https://lists.openembedded.org/g/openembedded-architecture/message/2326 Mute This Topic: https://lists.openembedded.org/mt/119158252/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
