One goal for the original dependency-graph support was to minimize it's impact on existing workflows, by operating transparently and not impacting the build outcome. This meant that any failures in dependency-graph generation or submission were logged as warnings, but did not cause the workflow to fail.
However, in some cases the primary purpose of a workflow is to generate and submit a dependency graph: in these cases it is desirable to have the workflow fail when this process breaks.
This PR introduces a new dependency-graph-continue-on-failure parameter, which when false will enable the latter behaviour. It also adds test coverage for different failures in dependency graph generation and submission.
One goal for the original dependency-graph support was to minimize it's impact on existing workflows, by operating transparently and not impacting the build outcome. This meant that any failures in dependency-graph generation or submission were logged as warnings, but did not cause the workflow to fail.
However, in some cases the primary purpose of a workflow is to generate and submit a dependency graph: in these cases it is desirable to have the workflow fail when this process breaks.
This PR introduces a new
dependency-graph-continue-on-failure
parameter, which whenfalse
will enable the latter behaviour. It also adds test coverage for different failures in dependency graph generation and submission.Fixes #1034 Fixes #997