-
Notifications
You must be signed in to change notification settings - Fork 149
feat: output action graph without execution #651
Comments
you can do this with gb list On Wed, 2 Nov 2016, 01:11 Stephan Heinze [email protected] wrote:
|
Not exactly: I do not want to know what packages are imported - I want to know what packages will be build. gb's cool feature is to build only those artifacts that experienced change in source files or in dependencies. Given a gb project providing 2 commands (separate executables) sitting in I got a project with lot of commands which will be packed into separate docker images in later stages. And I do not want to start all those pipelines - just those with a changed executable and not those which are still up-to-date. I hope you could follow :-) |
The dotfile produced by
gb build -dotfile build.dot
is quite cool.Given a project with multiple commands (multiple 'main' packages), I'd like find out which of them would be build with next
gb build
run and which are quite fine against the actual cache.Is there any chance to give the build command an
dry-run
option to produce no compiled/linked code but the action graph?Or just the package list of the to-be-build-packages on
stdout
whendry-run
is given but no dotfile requested.The text was updated successfully, but these errors were encountered: