In the CI for our build downstream, we extract the items from a build-order file that have overrides to construct another build-order file that is used in the test job. It could be useful to have that as an option to build-order instead so that a user could run fromager build-sequence --overrides-only $filename as a test job.
We also exclude some builds that take a particularly long time so we can parallelize the CI steps. It would be useful to have an --exclude option to support that.
For those long builds running in their own job, we extract the version information for a package from the build-order file using jq. It would be useful if we could pass a build-order file and package name(s) to a command and have it use the build-order file to control the order and versions of the packages built.
In the CI for our build downstream, we extract the items from a build-order file that have overrides to construct another build-order file that is used in the test job. It could be useful to have that as an option to build-order instead so that a user could run
fromager build-sequence --overrides-only $filenameas a test job.We also exclude some builds that take a particularly long time so we can parallelize the CI steps. It would be useful to have an
--excludeoption to support that.For those long builds running in their own job, we extract the version information for a package from the build-order file using jq. It would be useful if we could pass a build-order file and package name(s) to a command and have it use the build-order file to control the order and versions of the packages built.