• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Component/s: allure-plugin
• Labels:

  None
• Environment:

  Production

[JENKINS-63995] 401 errors from repo.jenkins-ci.org when downloading plugin

Kyle Pittman created issue - 2020-10-20 17:06

Kyle Pittman made changes - 2020-10-20 17:06

Summary

Original: 401 errors from repo.jenkins-ci.org when getting plugin

New: 401 errors from repo.jenkins-ci.org when downloading plugin

Kyle Pittman made changes - 2020-10-20 17:11

Description

Original: 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.   A workaround posted [here]([https://github.com/jenkinsci/allure-plugin/issues/273)] says to change the URL manually to point to the .tgz instead of the .zip file for the plugin and it will work.   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.

New: 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.   A workaround posted [here|https://github.com/jenkinsci/allure-plugin/issues/273)] says to change the URL manually to point to the .tgz instead of the .zip file for the plugin and it will work.   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.

Kyle Pittman made changes - 2020-10-20 17:24

Description

Original: 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.   A workaround posted [here|https://github.com/jenkinsci/allure-plugin/issues/273)] says to change the URL manually to point to the .tgz instead of the .zip file for the plugin and it will work.   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.

New: 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.

Collapse comment: louis yang added a comment - 2020-10-21 02:23

louis yang added a comment - 2020-10-21 02:23

also met this issue, please help to fix asap, thanks

Expand comment: louis yang added a comment - 2020-10-21 02:23

louis yang added a comment - 2020-10-21 02:23 also met this issue, please help to fix asap, thanks

Collapse comment: Gavin Mogan added a comment - 2020-10-21 04:36

Gavin Mogan added a comment - 2020-10-21 04:36

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?

Expand comment: Gavin Mogan added a comment - 2020-10-21 04:36

Gavin Mogan added a comment - 2020-10-21 04:36 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?

Collapse comment: louis yang added a comment - 2020-10-21 04:46

louis yang added a comment - 2020-10-21 04:46

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

Expand comment: louis yang added a comment - 2020-10-21 04:46

louis yang added a comment - 2020-10-21 04:46 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

Collapse comment: Gavin Mogan added a comment - 2020-10-21 04:54

Gavin Mogan added a comment - 2020-10-21 04:54

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.

Expand comment: Gavin Mogan added a comment - 2020-10-21 04:54

Gavin Mogan added a comment - 2020-10-21 04:54 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.

Gavin Mogan made changes - 2020-10-21 04:55

Component/s		New: allure-plugin [ 18926 ]
Component/s	Original: repo.jenkins-ci.org [ 23755 ]
Key	Original: INFRA-2782	New: JENKINS-63995
Workflow	Original: classic default workflow [ 246666 ]	New: JNJira + In-Review [ 246670 ]
Project	Original: Infrastructure [ 10301 ]	New: Jenkins [ 10172 ]

Collapse comment: Jesse Glick added a comment - 2020-10-21 12:12

Jesse Glick added a comment - 2020-10-21 12:12

Should have been fixed by https://github.com/jenkins-infra/crawler/pull/92.

Expand comment: Jesse Glick added a comment - 2020-10-21 12:12

Jesse Glick added a comment - 2020-10-21 12:12 Should have been fixed by https://github.com/jenkins-infra/crawler/pull/92 .

Jesse Glick made changes - 2020-10-21 12:12

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Load more newer events