-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Production
Within the past 12 hours or so all of our builds are failing due to a new 401 error when trying to download/use a plugin in our pipeline builds.
The URL that gives a 401 is: https://repo.jenkins-ci.org/maven-repo1/io/qameta/allure/allure-commandline/2.13.3/allure-commandline-2.13.3.zip
I have heard reports from others in chat that they are also having the same 401 error with different versions of the same plugin.
If you browse the parent folder https://repo.jenkins-ci.org/maven-repo1/io/qameta/allure/allure-commandline/2.13.3/ it does not show the .zip file at all, so I thought that possibly the file did not exist and the 401 error was just misleading. If I point the url to https://repo.jenkins-ci.org/maven-repo1/io/qameta/allure/allure-commandline/2.13.3/foo.zip then that gives a 404 as expected. So this means that the Allure .zip file DOES exist, and it is returning a 401 for some reason.
[JENKINS-63995] 401 errors from repo.jenkins-ci.org when downloading plugin
a 401 is because your not authorized.
https://repo.jenkins-ci.org/maven-repo1/last_updated.txt says feb of 2020
Why are you downloading non jenkins items from the jenkins artifactory? What builds is causing it to happen?
louis yang
added a comment - we use jenkins pipeline with allure plugin, it will use below url to install
java.io.IOException: Failed to install https://repo.jenkins-ci.org/maven-repo1/io/qameta/allure/allure-commandline/2.13.3/allure-commandline-2.13.3.zip to /home/jenkins/agent/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure_cmd
louis yang
added a comment - we use jenkins pipeline with allure plugin, it will use below url to install
java.io.IOException: Failed to install https://repo.jenkins-ci.org/maven-repo1/io/qameta/allure/allure-commandline/2.13.3/allure-commandline-2.13.3.zip to /home/jenkins/agent/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure_cmd are you building with allure, or building allure?
Cause it looks like https://github.com/jenkinsci/allure-plugin/search?q=allure-commandline is only downloading it from maven central on build, and copying it into the plugin itself. I don't see it hitting jenkins repo each time.
Looks like https://github.com/jenkinsci/allure-plugin/issues/273#issuecomment-712908011 has the proper workaround for what seems like a plugin that hasn't had a release in years.
Should have been fixed by https://github.com/jenkins-infra/crawler/pull/92.
Won't they need to "Check for updates" in order to retrieve the most recent results from the crawler?
JFrog asked us to reduce consumption on the hosted Artifactory per https://groups.google.com/d/msg/jenkins-infra/4B_jykZ2wi0/wrcszWE0BQAJ
In investigating it, we discovered INFRA-2772: Allure Plugin tool downloads caused 30% of all traffic to this service.
After the plugin maintainers hadn't responded to that issue and https://github.com/jenkins-infra/crawler/pull/78#issuecomment-707932926 for almost a week (and probably about 100GB of traffic later), I blocked the downloads from Artifactory.
The block will remain in place, but https://github.com/jenkins-infra/crawler/pull/92 means it won't affect builds (once any local metadata caches are updated).
Won't they need to "Check for updates" in order to retrieve the most recent results from the crawler?
Yes, tool installer metadata is updated at the same time as update center (i.e. plugin) metadata.
also met this issue, please help to fix asap, thanks