Dependency submission is not retried after GitHub HTTP error

[radoslaw-panuszewski]

In case GitHub responds with 503, the dependency submission silently fails and the SBOM is not published:

Warning: Failed to generate-and-submit dependency graph. Will continue.
HttpError: Dependency submission failed for ../../_temp/setup-gradle/build_publish-build-2.json.

Could we introduce a retry mechanism for that? Or at least fail the build instead of ignoring silently?

[bigdaz]

If you're using gradle/actions/dependency-submission, then failure to submit a dependency graph will trigger workflow failure.
If you're using gradle/actions/setup-gradle, you can enable this behaviour with the dependency-graph-continue-on-failure.

Retry on failure probably makes sense in both cases.

[radoslaw-panuszewski]

If you're using gradle/actions/dependency-submission, then failure to submit a dependency graph will trigger workflow failure. If you're using gradle/actions/setup-gradle, you can enable this behaviour with the dependency-graph-continue-on-failure.

Retry on failure probably makes sense in both cases.

Hi @bigdaz, I'm going to enable the dependency-graph-continue-on-failure flag - thanks for pointing it out!

Still, it would be awesome to have the retrying in place, especially that in all my cases the simple job rerun fixed the issue 😉