differently on different one.
Try out some of Ivan's suggests or other troubleshooting like that and
figure out how to isolate the problem.
Jeff Thompson
On 2/2/21 10:20 AM, Ivan Fernandez Calvo wrote:
>I have 2 different kind of jenkins agents.
>1. java web start
>2. ssh
>If the memo
using Java WebStart and you have no worries.
Jeff Thompson
--
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...@googlegroups.c
d a series of network protocols named "JNLP". Currently, the only
available one is "JNLP4-connect". This name is incorrect, as it has
nothing to do with JNLP. The misleading name is retained for backwards
compatibility purposes. The earlier versions of these protocols had a
varie
additional complexities of the Jenkins environment. This might show
where additional resources are needed. If that all passes, then continue
on to the additional troubleshooting steps involving the Jenkins
controller and agent.
Jeff Thompson
On 12/30/20 3:40 PM, jiga...@gmail.com wrote:
Interestingly
I did remove that long deprecated alias in Remoting 4.6 as part of the
Jenkins initiatives for improved terminology and diversity. I looked for
anything still depending on it, but may have missed something. I suggest
you see if you can determine which plugin is using the wrong term and
file a J
n
that would break the remoting. And I honestly have no idea how to
tackle that yet.
The master, as well as the slave are Windows server VM's running 6
executor slots each. The
tests we are running heavily use TCP communication.
Any idea how to tackle this ?
thx, M.
On Thursday, April 9, 2
how you launch the agent. Remoting system properties are
described at
https://github.com/jenkinsci/remoting/blob/master/docs/configuration.md
(naming for all these settings does not look to be very consistent...)
Unfortunately, that's the case.
Jeff Thompson
--
You received this message
amine what is happening on the master
and the agent during this time. Your issue sounds pretty weird. In my
experience, agent-initiated connections will keep retrying, so a timeout
is only a temporary delay.
Jeff Thompson
On 3/21/20 12:53 PM, JP wrote:
I have a jenkins agent / slave running as
Did you check the same settings as were mentioned earlier in this
discussion?
Otherwise, you would need to provide additional details such as
versions, changes, etc., for anyone to have a chance of helping you.
Jeff
On 2/17/20 7:47 AM, Sat wrote:
I am facing the same issue today.
For Jenkin
still needed, the capabilities could be pulled out of core into a
plugin, maintained by someone that uses it.
Jeff Thompson
--
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 i
On the agent (node) configuration page when configuring to "Launch agent
by connecting it to the master" there is an Advanced button. If you
click that, one option that becomes visible is "Tunnel connection
through". This *might* work for you. Read the inline help and try it to
see if it meets
around or something. Maybe
something as simple as "Jenkins is starting". I'm not sure that the
"Please wait while" really provides value. Other possible word choices
instead of "starting" include "loading" and "launching" but I think
"sta
7;s work with
WebSockets. Both efforts can proceed independently.
I'm still working on a timeline for when these changes will go in.
Currently I'm leaning towards waiting a little before making this change.
Jeff
On 12/3/19 11:58 AM, Slide wrote:
I'm a big +1 on this.
On Tu
/2c137aa7884fd6360f133964422fd997351a7ebb/jep//README.adoc
) This may cover use cases where someone still uses the older protocols.
We could make the removal of the old protocols dependent on completion
of WebSocket support.
Jeff Thompson
--
You received this message because you are
filesystem issue and
not be related specifically to the userid migration. I wonder if the bug exists
in more current versions of Java.
Jeff Thompson
> On Mar 22, 2019, at 6:45 PM, Marc Esher wrote:
>
> Hi all, thanks for the advice. Apologies for not posting back to the group
> ear
You could try disabling the new, more secure capabilities by setting the
DISABLE_USER_SEED system property to true. That might allow you to get 2.160
working for you, in a less secure fashion.
There is no indication that logins are generally broken, but you’ve apparently
hit some unusual config
luck on troubleshooting your system configuration.
Jeff Thompson
> On Jan 9, 2019, at 6:37 AM, SysInt wrote:
>
> Does somebody need further piece of information to help me figure this out ?
>
> --
> You received this message because you are subscribed to the Google Groups
from others with experience using the
different mechanisms.
Jeff Thompson
> On Dec 4, 2018, at 1:48 PM, Slide wrote:
>
> FYI, even though the term is used in some places in the docs and code
> (because it's hard to change everything), "agent" is the requested term
I suggest you try configuring it at the configuration page for the node in
Jenkins. Look under the Advanced button for JVM options.
Jeff Thompson
> On Nov 27, 2018, at 7:32 AM, gotviser...@gmail.com wrote:
>
> We have a Windows 2016 Slave. The slave gets disconnected due to he
tokens as Matthew
mentions. If you revoke all tokens and then discover some processes or agents
can no longer connect and authenticate, then you’ll need to perform that
re-configuration after the fact.
Jeff Thompson
> On Sep 21, 2018, at 10:56 AM, matthew.web...@diamond.ac.uk wrote:
>
>
20 matches
Mail list logo
