Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
403 for build-info-extractor-gradle-4.15.2-uber.jar
See original GitHub issueI’m using jFrog CLI v1.39.7 to upload an Android .aar library to Artifactory (because newer version do not support yet) and it was working fine, but now I get this message:
$ ./jfrog rt gradle-config --use-wrapper=true --repo-resolve=$GRADLE_REPO_KEY --server-id-resolve=Default-Server --repo-deploy=$GRADLE_REPO_KEY --server-id-deploy=Default-Server # collapsed multi-line command
[Info] gradle build config successfully created.
[Info] Downloading bintray/jcenter/org/jfrog/buildinfo/build-info-extractor-gradle/4.15.2/build-info-extractor-gradle-4.15.2-uber.jar
[Error] 403 Forbidden
ERROR: Job failed: exit code 1
Have you lock the access to that file?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, you’d be running before your gradle config. In your case, you’d be looking at
export JFROG_CLI_JCENTER_REMOTE_SERVER=Default-Serverexport JFROG_CLI_JCENTER_REMOTE_REPO=$GRADLE_REPO_KEYYou’d be sending it through the same repo you using for your build config. This assumes you have jcenter in your gradle repo.
Thank you very much! Now I can upload artifacts to Artifactory again!
I’m closing this issue