-
Bug
-
Resolution: Fixed
-
Critical
-
happens again with:
Jenkins 2.289.2
and Jenkins 2.300 on RHEL 8 and installed Allure Jenkins Plugin Version 2.29.0
and Jenkins 2.289.2 on Windows and installed Allure Jenkins Plugin Version 2.29.0
Initial Reported Env:
Jenkins: 2.205
Root node: CentOS 7 (el7)
Agents: macOS Mojave connected through JNLP4.happens again with: Jenkins 2.289.2 and Jenkins 2.300 on RHEL 8 and installed Allure Jenkins Plugin Version 2.29.0 and Jenkins 2.289.2 on Windows and installed Allure Jenkins Plugin Version 2.29.0 Initial Reported Env: Jenkins: 2.205 Root node: CentOS 7 (el7) Agents: macOS Mojave connected through JNLP4.
Upon updating to Jenkins 2.205, our Jenkins setup became unable to get plugin updates.
I see the following error now:
"There were errors checking the update sites: None of the tool installer metadata passed the signature check"
update from thomaspatzig
happens again with Jenkins 2.289.2
response / JSON of update URL looks invalid
does the update service works properly?
https://updates.jenkins.io/update-center.json
http://updates.jenkins.io/update-center.json
http://updates.jenkins.io/current/update-center.json