It seems like <gradle/actions v3.4.0> broke build ...
# develocity
k
It seems like gradle/actions v3.4.0 broke build scan publishing for us. Anyone else experiencing issues with this? I even tried providing the key via the new input parameter but it still behaves as if no key is provided.
d
Sorry to hear that Kyle. Can you share a snippet of how your are configuring Develocity?
k
Untitled
d
Thanks. Do you see any error messages reported in your workflow?
k
Copy code
Publishing build scan...

The Develocity server (grad.le.comcast.net) rejected the request due to authentication being required.
If you are able to sign in to this server in a web browser, you can authenticate your environment by running the following task:

:provisionDevelocityAccessKey

Or see https://gradle.com/help/gradle-plugin-authenticating for additional help with authenticating your build environment.

The remote build cache was disabled during the build due to errors.
d
Anything in the GitHub Actions page itself?
(Not the Gradle logs?)
k
ah yes…
so that was after trying to set the input parameter. let me check the run before.
Hmm same warning.
d
Does your
DEVELOCITY_ACCESS_KEY
contain multiple server entries? Like
server1=xxxx;server2=yyyy
?
(If you know)
k
nope just a single one
d
OK thanks. This is clearly a bug, and we'll get a fix out soon. In the meantime there's a workaround: pass the
DEVELOCITY_ACCESS_KEY
env var directly in the step that invokes Gradle. The
setup-gradle
step is blanking it out.
k
I tried passing it directly like so:
Copy code
- name: Set up Gradle
        uses: gradle/actions/setup-gradle@d9336dac04dea2507a617466bc058a3def92b18b # v3.4.0
        with:
          develocity-access-key: ${{ secrets.DEVELOCITY_ACCESS_KEY }}
but that didnt work. You mean do something like this:
Copy code
- name: Set up Gradle
        uses: gradle/actions/setup-gradle@d9336dac04dea2507a617466bc058a3def92b18b # v3.4.0
        env:
          DEVELOCITY_ACCESS_KEY: ${{ secrets.DEVELOCITY_ACCESS_KEY }}
ooh you mean like this
Copy code
- name: Compile
        run: >
          ./gradlew
          app:compileReleaseJavaWithJavac
          --info
        env:
          DEVELOCITY_ACCESS_KEY: ${{ secrets.DEVELOCITY_ACCESS_KEY }}
Thats going to suck because we have a ton of steps that invoke gradle commands so we rely on the workflow level configured env variable. I guess I will roll back the upgrade for now.
d
It might also work if you use the (deprecated)
GRADLE_ENTERPRISE_ACCESS_KEY
instead of
DEVELOCITY_ACCESS_KEY
. (With no other change to your original workflow)
k
That didnt seem to work either
d
OK downgrade is your only option right now. We are working on a fix.
👍 1
v3.4.1 has been released with a fix for this issue. Please try it out and let us know if it works for you.