-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[install-plugins.sh] Try other url when 1 fails #373
Labels
Comments
Here is the little bash function I use as a work-around:
I just replaced the |
elouanKeryell-Even
changed the title
[install-plugins.sh] Try other mirror when 1 fails
[install-plugins.sh] Try other url when 1 fails
Oct 21, 2016
having same problem. seems like the install-plugins.sh needs more refinement, i myself had to alter the script due to its curl command lacking extended timeout and retry enhancment. |
carlossg
added a commit
to carlossg/jenkins-ci.org-docker
that referenced
this issue
Feb 5, 2018
curl may fail if mirror is flaky or unreachable They retry will likely get another mirror
carlossg
added a commit
to carlossg/jenkins-ci.org-docker
that referenced
this issue
Feb 5, 2018
curl may fail if mirror is flaky or unreachable They retry will likely get another mirror
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For a reason that I don't understand, I am having connectivity problems with one of the servers hosting jenkins plugins, namely
icm.edu.pl
.When downloading plugins,
mirrors.jenkins-ci.org
shows a list of several urls for the resource I am looking for (HTTPLink
headers), and chooses one for me (HTTPLocation
header).Sometimes it works fine:
Other times, when
mirrors.jenkins-ci.org
tells me to download from the particular server that I can't reach, it will fail:I was thinking maybe the downloading section of the script could be strengthened by trying those other urls in the
Link
headers, when the 1st one does not work.I know this might be a little over-the-top, since nearly nobody should be affected by those kind of rare connectivity problems, but I thought I should mention it anyway :)
The text was updated successfully, but these errors were encountered: