For the sake of completeness, this turned out to be blocked at our firewall
based on a list of banned IP addresses. This still seems strange as I was
able to curl the update files directly from that machine without issue.
The firewall (Palo Alto) seemed to not like the redirects to mirrors and
ter
I changed the configuration to point directly to /home/jenkins (plugin
installs still fail) and then added the freestyle job as you suggested
which successfully created and deleted the file at the path suggested, so
it appears permissions are not the problem.
On Mon, Feb 3, 2020 at 3:32 PM Mark Wa
Looks like our not open / url blocked.
Try to access the Jenkins update plugin url or test it with the curl
command and you should noticed that it is blocked. If blocked opening the
firewall / proxy policy to allow the Jenkins update url may help you
overcome the problem.
You may have to do this
We had a similar error (failed to download plugins) last week (see my post
in this list) and it occurred several times on our instances.
Am Di., 4. Feb. 2020 um 03:36 Uhr schrieb Steve Rogers <
steve.cg...@gmail.com>:
> That was my first guess too. I tried with both.
>
> On Mon, Feb 3, 2020 at 7:
That was my first guess too. I tried with both.
On Mon, Feb 3, 2020 at 7:22 PM Jan Monterrubio
wrote:
>
> Could it be an http vs https problem? We had some of those with maven
> before.
>
> On Mon, Feb 3, 2020 at 16:05 Steve Rogers wrote:
>
>> I'll give that a try. I believe /opt/tomcat/.jenki
Could it be an http vs https problem? We had some of those with maven
before.
On Mon, Feb 3, 2020 at 16:05 Steve Rogers wrote:
> I'll give that a try. I believe /opt/tomcat/.jenkins was the default. I
> then just linked that to /home/jenkins. Our old system where I am getting
> the same error
I'll give that a try. I believe /opt/tomcat/.jenkins was the default. I
then just linked that to /home/jenkins. Our old system where I am getting
the same error is a windows install, so it seems more likely something in
our network.
Thanks for your help.
On Mon, Feb 3, 2020 at 3:32 PM Mark Wai
That's surprising. Could you check the permissions from inside Jenkins by
creating a freestyle job that runs on master and attempts to create and
delete a file named /opt/tomcat/.jenkins/plugins/script-security.jpi.tmp ?
For me, the directory name '/opt/tomcat/.jenkins/' is surprising. Most
Jenki
Yes, plenty of space and permissions are correct. I should have added in
the original that I can install manually by downloading the plugin file
directly and then uploading into jenkins.
On Mon, Feb 3, 2020 at 2:50 PM Mark Waite wrote:
> It may be worth checking the directory permissions to con
It may be worth checking the directory permissions to confirm that the
Jenkins user can still write to that directory. You may also want to check
that the disc has available free space and available inodes to allow new
files to be created.
On Mon, Feb 3, 2020 at 3:42 PM Steve Rogers wrote:
> An
10 matches
Mail list logo
