Unable to publish artifacts after enabling gradle caching

[BelgianDev]

Description:
I enabled gradle caching in the setup java task for my action, first publishing worked nothing weird. But after changing code and wanting to make a new snapshot build of one of my libs it won't publish I constantly get a Received status code 403 from server: Forbiddenno matter what I do even disabling the caching won't make the issue go away.

I'm publishing to a self-hosted repo even after providing administrator permissions on Nexus the action was only able to publish 2 files before getting a 403 forbidden.

This issue does not happen when I publish from my own computer it only happens when running in the GitHub action.
I'm still not sure a 100% if the caching is at fault or something else but I've been fighting for over a week and can't seem to fix the issue.

Task version:
actions/setup-java@v4

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:

1. Create a simple action to publish libraries to a Nexus Repository or any repository. (Here is Mine)
2. In the workflow enable gradle caching.
3. Publish artifacts (Works as expected)
4. Make changes for a new commit
5. Publish artifacts -> Fails, server returns a 403 error.
6. Disable caching and recommit
7. Republish failed artifacts -> Still fails.

Expected behavior:
That I will be able to publish my artifacts

Actual behavior:
A description of what is actually happening.

[aparnajyothi-y]

Hello @BelgianDev, Thank you for creating this issue and we will look into it :)

[priya-kinthali]

Hello @BelgianDev 👋,
We have attempted to reproduce the error but were unable to do so. It appears that the issue may be related to Gradle caching or Nexus repository permissions. Here are some potential workarounds that might help resolve your issue:

• Gradle Caching Configuration: Consider using the cache: 'gradle' input with setup-java in your workflow to cache Gradle dependencies, speed up the build, and prevent re-downloads. For more details, please refer to the caching Gradle dependencies documentation.

• Debug Logging: Enable debug logging by adding the ./gradlew publish --info command to get more detailed output or set ACTIONS_STEP_DEBUG to true as detailed here. The logs might provide more insight into the issue you are encountering, such as missing permissions or incorrect paths.

• Nexus Repository Permissions: Ensure that the credentials for the Nexus repository are correctly configured in the Gradle script and that there are no IP restrictions or other security settings blocking the requests.

We hope these suggestions help resolve your issue. Please let us know if you need further assistance or if the issue persists. We are here to help!