>
> Jenkins requires Java7 or later, but you are running 1.7.0_25-b17 from
> C:\Program Files (x86)\Jenkins\jre
It looks like Jenkins now requires Java8, but the error message is still
behind? How do I update Jenkins' Java version, since it only updates the
.war file?
Thanks,
Jeremy
--
You
Like many enterprise servers, my Jenkins server does not have Internet
connectivity.
Updating plugins is always a tedious bit of work to see what plugins have
new versions in the Update Center, and then going to
http://updates.jenkins-ci.org/download/plugins/ to find them by their
folder name,
> Then go to the Security Tab, and click on edit site list. Add your
> jenkins base address there
>
> ------
> *From: *"Jeremy Morton" >
> *To: *jenkins...@googlegroups.com
> *Sent: *Wednesday, January 15, 2014 2:22:08 PM
> *Subject: *Re:
Even worse, even if you don't update Java, it refuses to run self-signed
jnlp files because you aren't running the latest version [and the latest
version blocks them, too].
On Wednesday, January 15, 2014 3:10:15 PM UTC-5, Jeremy Morton wrote:
> FYI, as of Update 51, it now b
M, Mark Waite <*mark.ea...@gmail.com*> wrote:
> You can download slave.jar from the link on each slave node definition
> page. It is available from
> *http://localhost:8080/jnlpJars/slave.jar*<http://localhost:8080/jnlpJars/slave.jar>(replace
> localhost with your Jenkins server
Rolling back to Jenkins.war.bak [1.539] fixed this.
On Monday, December 2, 2013 3:37:55 PM UTC-5, Jeremy Morton wrote:
>
> I haven't been able to start Jenkins today:
>
> Dec 02, 2013 3:36:18 PM jenkins.InitReactorRunner$1 onAttained
> INFO: Prepared all plugins
>
I haven't been able to start Jenkins today:
Dec 02, 2013 3:36:18 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Dec 02, 2013 3:36:19 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Dec 02, 2013 3:36:19 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmen
>java -jar slave.jar -jnlpUrl
> https://ci.domain.com/jenkins/computer/COMPUTERNAME/slave-agent.jnlp
>
>
>
> Den tisdagen den 29:e oktober 2013 kl. 19:25:12 UTC+1 skrev Jeremy Morton:
>>
>> When I run the javaws.exe command line to start slave-agent.jnlp, I now
>>
Email notifications at the end of Job2 are one of the things that cause it
to wait for all previously started runs to finish in order to compare
results. :(
On Friday, November 15, 2013 12:58:17 PM UTC-5, James Nord (jnord) wrote:
>
> That’s not the flow that’s stopping it but job2.
>
>
>
> M
When I run the javaws.exe command line to start slave-agent.jnlp, I now get
this Security warning from Java, which implies that in a future Java
update, I won't be able to run it at all.
Is this something that I need to configure to make Java happy, or is this a
Jenkins-side fix?
Security W
I am seeing it not work with Build Flow jobs, either.
Jenkins 1.534
Throttle Concurrent Builds version: 1.8
--
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 j
My high-level scenario is that I have a pool of slave machines that I want
to run tests on, but I need to use two machines for each run [one acting as
a client, one acting as a server]. I would like to have it choose two
machines from the pool and then run the tests on them, keeping other test
12 matches
Mail list logo
