Fail build step if Gradle version does not support dependency graph generation #1034
Milestone
Comments
bigdaz
added a commit
that referenced
this issue
Jan 13, 2024
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. Fixes #1034 Fixes #997
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
If the primary purpose of a workflow is to generate and submit a dependency graph, then the workflow should fail if this isn't achieved. Presently, the behaviour is to warn and continue.
We could add an option like
dependency-graph-continue-on-failurethat defaults to true (for now), but can be switched to false so that Gradle version and permission issues cause the workflow to fail, rather than simply warning.The text was updated successfully, but these errors were encountered: