On 24.03.2015, at 11:59, Clifford Sanders wrote:
> Thanks Daniel. I also found this related Jira isuue:
>
> "Auto-installer for JDK no longer works":
> https://issues.jenkins-ci.org/browse/JENKINS-26780
Right, it contains a bit of background info. Note that that was before the
version that n
Thanks Daniel. I also found this related Jira isuue:
"Auto-installer for JDK no longer works":
https://issues.jenkins-ci.org/browse/JENKINS-26780
Am Dienstag, 24. März 2015 11:50:05 UTC+1 schrieb Daniel Beck:
>
>
> On 24.03.2015, at 11:39, Clifford Sanders > wrote:
>
> > Is there a Jira issue
On 24.03.2015, at 11:39, Clifford Sanders wrote:
> Is there a Jira issue for the fix in 1.596? The original poster wrote that
> the error still occures in 1.599.
I got the versions wrong, it's 1.596.1 (LT)S and 1.600 that are fixed. They
require the administrator to disable browser-based down
Updating or restarting can't be done during office hours.
I solved it by copying the file 'hudson.tools.JDKInstaller' from my local
Jenkins to the 'updates' directory on the remote Jenkins.
Is there a Jira issue for the fix in 1.596? The original poster wrote that
the error still occures in 1.5
>
> Then I looked at the file 'hudson.tools.JDKInstaller' that was mentioned in
> the issue. The contents was exactly the same as the file
> 'hudson.tasks.Maven.MavenInstaller' which is very strange but could be the
> reason for the error.
Fixed in 1.596 with server-based download.
> I delete
clicking on 'Check Now' didn't help and we are located in Germany.
As Jenkins is started with '--logfile=/home/jenkins/logs/jenkins.log' you
mean this logfile? Nothing relevant in there.
I downloaded jenkins-1.594.war and started it locally. The drop-down was
populated with all JDKs.
I found t
Go to Manage Jenkins » Manage Plugins » Advanced and click 'Check Now'.
If that doesn't help, check the log at /log/all for possibly relevant messages.
Are you in China or a neighboring country?
On 24.03.2015, at 09:59, Clifford Sanders wrote:
> We use version 1.594 and have the same problem.
The JDKs that were already configured to download from java.sun now all
have the same 'JDK ID': jdk-8u40-oth-JPR (see attached screenshot)
Clifford
Am Dienstag, 24. März 2015 09:59:37 UTC+1 schrieb Clifford Sanders:
>
> We use version 1.594 and have the same problem. I attached a screenshot.
>
>
We use version 1.594 and have the same problem. I attached a screenshot.
Clifford
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@g
Might be worth sharing the error you are seeing as its hard to diagnose in
the dark :)
Richard.
On Thu, Feb 19, 2015 at 9:42 AM, Sean Last wrote:
> not compiling jenkins. Getting jenkins to download the JDK from oracle.
> However, it appears that even though I can ping and wget from all
> appr
not compiling jenkins. Getting jenkins to download the JDK from oracle.
However, it appears that even though I can ping and wget from all
appropriate servers on this vagrant image, jenkins itself can't reach out
for some reason Which is weird, because I've never had a problem before.
On Wedn
It may be best to ask questions about compiling Jenkins with a specific JDK
on the jenkins-dev mailing list.
There were issues in the past when compiling with Java 8. I believe the
shipped Jenkins compiles with Java 7.
On Wed, Feb 18, 2015 at 1:11 PM, Sean Last wrote:
> And it throws an error
And it throws an error about not having any data if you try and build with
a new java version.
Anyone seen this? Any ideas?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, s
13 matches
Mail list logo
