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

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.

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.

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.

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 ]

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

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

Jenkins