Yes, I can get the right location via curl -I 
-Lhttps://get.jenkins.io/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi


But I’m not sure why it’s still super slow sometimes. Perhaps it’s slow when we 
try to resolve this domain get.jenkins.io


| | |
|
|
|


On 11/17/2020 22:52,'Olblak' via Jenkins 
Developers<[email protected]> wrote:
> Because all plugins URL point to 
> https://updates.jenkins.io/download/plugins/xxx instead of the mirror.  



And then you are redirected to mirrors



curl -I -L 
https://get.jenkins.io/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi

HTTP/1.1 302 Found

Date: Tue, 17 Nov 2020 14:50:34 GMT

Server: Mirrorbits/v0.5.1

Cache-Control: private, no-cache

Content-Type: text/html; charset=utf-8

Link: 
<https://mirror.gruenehoelle.nl/jenkins/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi>;
 rel=duplicate; pri=1; geo=nl

Link: 
<https://ftp-nyc.osuosl.org/pub/jenkins/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi>;
 rel=duplicate; pri=2; geo=us

Link: 
<https://mirror.serverion.com/jenkins/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi>;
 rel=duplicate; pri=3; geo=us

Link: 
<https://ftp-chi.osuosl.org/pub/jenkins/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi>;
 rel=duplicate; pri=4; geo=us

Link: 
<https://mirror.xmission.com/jenkins/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi>;
 rel=duplicate; pri=5; geo=us

Link: 
<https://mirrors.tuna.tsinghua.edu.cn/jenkins/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi>;
 rel=duplicate; pri=6; geo=cn

Link: 
<https://ftp.yz.yamagata-u.ac.jp/pub/misc/jenkins/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi>;
 rel=duplicate; pri=7; geo=jp

Location: 
https://ftp.halifax.rwth-aachen.de/jenkins/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi

Via: 1.1 get.jenkins.io



HTTP/2 200

server: nginx/1.14.2

date: Tue, 17 Nov 2020 14:50:35 GMT

content-type: application/octet-stream

content-length: 613574

last-modified: Fri, 16 Oct 2020 07:26:25 GMT

accept-ranges: bytes











On Tue, Nov 17, 2020, at 3:44 PM, Rick wrote:





Because all plugins URL point to 
https://updates.jenkins.io/download/plugins/xxx instead of the mirror.  

|
|
|
|
|
|


On 11/17/2020 22:40,Tim Jacomb<[email protected]> wrote:

Why don’t the regular files work? Users should be directed to a Chinese mirror 
already, is it the distance to get the redirect?



On Tue, 17 Nov 2020 at 14:02, Rick <[email protected]> wrote:



Yes, we just need to change the URL of plugins.



You mean generate two or more versions of update-cener.json files? For example, 
update-center.json and update-center-zh.json ? Am I right?









On 11/17/2020 21:57,Daniel Beck<[email protected]> wrote:





On 17. Nov 2020, at 14:48, Rick <[email protected]> wrote:



I try to modify the URL plugins into a mirror one. But it's unavailable due

to security reasons. Jenkins will do the validation with update-center.json

file. In order to fix this, I just make my own certificate file. Before

using it, you need to download the certificate file into your Jenkins. It's

still very inconvenient for many users.



So, I was wondering if I can get permission of accessing the official

certificate file. People just don't need to do anything besides changing

the URL of the update center. I know this file should not share with

someone who is not a member of the Jenkins infra team. Because it's very

important for all Jenkins users. An alternative solution is that we store

the certificate file in a safe place. For example, store it in the GitHub

secret.



If the only change is download URLs that point to a site in China, we can look 
into generating appropriately modified files in the regular update center which 
you can then pull without modification.



--

You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].

To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/D60E8D5F-A3E0-4FB1-A815-F0A28B7FEA37%40beckweb.net.







--

You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].

To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/44f497ab.6a8f.175d683041f.Coremail.zxjlwt%40126.com.





--

You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].

To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieGO-irB1C7U0ct4eZ%2BXabp1Jy4Mfsu0Wy8JUPjLKznOA%40mail.gmail.com.





--

You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].

To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3b80874e.6b81.175d6aa52e8.Coremail.zxjlwt%40126.com.




--
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/300b9abe-c22b-4a65-af7d-7676ab50c514%40www.fastmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5555c3f8.6bd0.175d6b6bfbb.Coremail.zxjlwt%40126.com.

Reply via email to