Closed networkandcode closed 3 years ago
+1
Same here:
Jenkins 2.235.5
Allure plugin version: 2.28.1
Allure commandline version: 2.13.6 and 2.12.1
Is this project still alive?
Similarly:
ERROR: Step ‘Allure Report’ aborted due to exception:
java.io.IOException: Server returned HTTP response code: 401 for URL: https://repo.jenkins-ci.org/maven-repo1/io/qameta/allure/allure-commandline/2.8.1/allure-commandline-2.8.1.zip
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1876)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2982)
at java.net.URLConnection.getHeaderFieldLong(URLConnection.java:629)
at java.net.URLConnection.getContentLengthLong(URLConnection.java:501)
at java.net.URLConnection.getContentLength(URLConnection.java:485)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getContentLength(HttpsURLConnectionImpl.java:398)
at org.jvnet.robust_http_client.RetryableHttpStream.<init>(RetryableHttpStream.java:90)
Same here! any workaround?
java.io.IOException: Server returned HTTP response code: 401 for URL: https://repo.jenkins-ci.org/maven-repo1/io/qameta/allure/allure-commandline/2.13.2/allure-commandline-2.13.2.zip at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1900) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:268) at java.net.URL.openStream(URL.java:1068) at hudson.FilePath$Unpack.invoke(FilePath.java:948) at hudson.FilePath$Unpack.invoke(FilePath.java:942) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3073) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
This has now fixed itself for me, my logs are generating fine now in Jenkins.
seems some one's fixed it, thanks :)
Problem is reproducing again. Basic auth on https://repo.jenkins-ci.org/maven-repo1/io/qameta/allure/allure-commandline/2.8.1/allure-commandline-2.8.1.zip
Should we reopen this issue (it is currently closed) or open a new one?
Fast solution: Global Tool Configuration -> Allure Commandline -> Add Installer -> Extract .zip/.tar.gz -> https://repo1.maven.org/maven2/io/qameta/allure/allure-commandline/2.13.6/allure-commandline-2.13.6.tgz (or other version you need)
I can confirm that the below configuration in the Global Tools works, thanks:
I was told in a Jenkins chat that this may have been implemented and may be the cause of the errors: https://groups.google.com/g/jenkins-infra/c/4B_jykZ2wi0
If this is the case, then pointing to maven sounds like the right fix.
ok so repo1.maven.org/maven2/ (given manually as mentioned by @vanangelov) .... works but repo.jenkins-ci.org (which is when the mvn central repo option is selected) .... doesn't
See #274.
Issue
Context
Jenkins version: 2.249.2
Job type: Pipeline
Allure plugin version: 2.28.1
Allure commandline version: 2.13.1
Problem description
The allure plugin stopped working a while ago,
Trace here: