Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Won't Do
-
Component/s: artifactory
-
Labels:None
-
Similar Issues:
Description
Not sure this is actually artifactory but rather our NGINX reverse proxy.
Basically https://repo.jenkins-ci.org/public/ returns a 405 error code.
This means that Nexus will block the repository as it is an unexpected return code for the root of the repo. It is comon for companies and individuals to run a nexus instance infront of other third party repos.
This has regressed at some point just before the Christmas break and now.
Attachments
Attachments
Activity
I hit it as well.
We run an nginx proxy only for Azure-based agents for ci.jenkins.io, which is located at repo.azure.jenkins.io.
This appears to be yet-another-issue with Artifactory Online.
indeed. using https://jenkinsci.jfrog.io/jenkinsci/public also gives a 405
it's like they are actively trying to break Nexus users ;-p
OT: - who does the reverse from https://repo.jenkins.io to artifactory online then?
I doubt they will repsond. they didn't last time they broke Nexus caches infront of them, but https://twitter.com/JamesTeilo/status/948241747917922306
not sure we have any support with them...
Well, Artifactory support definitely tried to help us with INFRA-1447.
And they sponsor us, so probably we should not grumble in the current state
Thank you for contacting JFrog Support.
We have experienced performance difficulties with some servers, including jenkins-ci. Please be advised that in the meantime, to mitigate this, we have blocked the directory browsing for https://repo.jenkins-ci.org/public. You may still use this repository for uploading and downloading files. In addition, we improved performance related to Access service.
repo.jenkins-ci.org is currently up and running.
Flag added
Good catch James Nord, I emailed JFrog support about lifting the restriction
Is there an update to this issue?
We are currently unable to build projects because of the 405 error, preventing the download of jar files.
Works for most team members as long as they have the jar locally in their maven repository, but people needing to download it simply cannot.
Arne De Herdt most likely you are using a Nexus in front of the Jenkins repos, as Maven itself doesn't care.
Ask your Nexus admin to temporarily disable "Auto Blocking Enabled" for it.
I'll forward the information and see if it helps.
However, when I try to access the Jenkins Repo, I still get the 405 however.
So if our Nexus is missing the jar, we will still run into the same problem however.
Arne De Herdt you only get the 405 on the root page.
downloading artifacts and browsing anywhere not the root is unaffected.
e.g. https://repo.jenkins-ci.org/public/org/jenkins-ci/main/
From JFrog:
Following up on my last email, we wanted to share with you that we are planning
to deploy the fixed version to your instance on next Sunday, the 14th, (during
Israel daytime hours). When the deployment is done, we will perform our
validations, and remove the /public directory browsing restriction.
James Nord Is this still an issue?
LGTM
Sascha Retter Please explain why you care.
Daniel Beck we're operating a nexus proxy-repository for jenkins-plugin development.
Sascha Retter As I've told James Nord out of band I'm telling you now:
Please don't murder our Artifactory. You're not the only one using it, and proxying the virtual repo is really expensive.
https://repo.jenkins-ci.org/api/repositories/public is a JSON response that lists the actual repos included in this virtual one.
The only ones we deployed anything to in the last five years are snapshots and releases. so those should be mirrored/proxied.
Apparent lack of legitimate use case.
Daniel Beck thanks for elucidation! It was not transparent to us that this is a virtual repo.
Sascha Retter Arne De Herdt if you have a commercial nexus please file a support ticket with Sonatype and reference (ZD-23504 which is from a different customer so you will not be able to see but they will).
If you don't have a commercial contract (and possibly even if you do) please vote for https://issues.sonatype.org/browse/NEXUS-9508
From Nexus log:
From Chrome: