Fail nicely if dependency-submission and setup-gradle are used together in the same Job

[Bert-R]

I'm trying to get dependency submission to work through the PR yonadev/yona-server#1289, but it fails with this error:

FAILURE: Build failed with an exception.

* What went wrong:
Task 'ForceDependencyResolutionPlugin_resolveAllDependencies' not found in root project 'yona-server'.

The dependency submission task is defined as follows:

      - name: Publish Gradle dependencies
        uses: gradle/actions/dependency-submission@v3
        with:
          build-root-directory: yona-server

The action to build the project is successful and is defined straight before the dependency submission. That looks as follows:

      - name: Build and analyze
        uses: gradle/actions/setup-gradle@v3
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}  # Needed to get PR information, if any
          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
        with:
          build-root-directory: yona-server
          add-job-summary-as-pr-comment: on-failure
          arguments: |
            check
            sonarqube
            --info

We are running Gradle 7.5.1

Your help is appreciated!

[jeff-tyl]

I had this error with Gradle 8.2 as well and found by moving the dependency review submission to a separate job it worked. The submission action does not depend on any build steps, so it can run in parallel with the build. I started with the sample job definition provided and had to add the proper Java version setup as well as making gradlew executable.

[Bert-R]

That indeed fixes it. Thanks for the tip! Still, I feel it i's a bug: it makes sense to combine the two in one workflow and the documentation does not state you cannot.

[bigdaz]

Thanks for the report. We should certainly make this work, or improve error reporting when you attempt to use setup-gradle and dependency-submission in the same Job.

[Bert-R]

Thanks for the quick and thorough follow-up!