Re: How do you set java options for ssh agents

Bjorn I like that explanation. If this behaviour is "as designed" then I just need to adjust my expectations. I suspect that my Ansible playbooks are not relaunching the agent processes when changes happen. The agent options are specified through the JCasC yaml in the master/controller, and I

Re: How do you set java options for ssh agents

I think this is simply because the agent process survives the master restart (that is actually a feature) so if agent settings change, you need to disconnect and connect the agent (or otherwise restart the agent process to pick up the changes). timb...@gmail.com schrieb am Freitag, 25.

Re: How do you set java options for ssh agents

Thanks. I believe you were saying stop/start because you're using Docker container. In your Docker example, stopping and restarting the Docker container is analogous to rebooting (power cycling, or sudo rebooting) the physical or virtual machine hosting the Jenkins service. In this thread I'm

Re: How do you set java options for ssh agents

Restart Jenkins using the CLI(https://www.jenkins.io/doc/book/managing/cli/) it is the same make it from the UI. When I said stop/start, I mean stop/start the Jankins daemon/service/Docker container/Whatever. The reason it is because IIRC JCasC runs on the start time of the Jenkins process, and

Re: How do you set java options for ssh agents

Thanks. What's the difference between "restart Jenkins from UI" and "stop the Jenkins instance and start it again"? In the latter, how are you implying that Jenkins gets stopped and restarted, through the CLI? Just trying to understand what you're saying - it sounds like you're implying CasC

Re: How do you set java options for ssh agents

ok, I think I know what happens, I saw it before using Docker and JCasC, if you make changes on the JCasC and restart Jenkins from UI the changes are not applied because JCasC is not executed on that restart, but if you stop the Jenkins instance and start it again the changes are applied IIRC

Re: How do you set java options for ssh agents

I will configure a test environment with JCasC that has jmvOptions too see how it behaves, then we will know if it is an issue or not, in any case is weird. El El mié, 23 sept 2020 a las 22:10, Tim Black escribió: > More info: In my case, a reboot is definitely needed. A > disconnect/reconnect

Re: How do you set java options for ssh agents

More info: In my case, a reboot is definitely needed. A disconnect/reconnect does not suffice, nor does rebooting just the master/controller or the agent in sequence - *the only way I see the correct jvmOptions being used is by rebooting the entire cluster at once*. I'm using Jenkins 2.222.3,

Re: How do you set java options for ssh agents

Thanks everyone, it's working now (see below for details). kuisathaverat, these agents have 96GB total RAM. Thanks for the explanation. Our builds are very RAM intensive, and I misunderstood that the builds happened within the remoting java process. Sounds like you're saying in this case

Re: How do you set java options for ssh agents

I think to have those updated settings applied correctly we need to disconnect and launch those agents again instead of just bringing those offline and online, just checking to make sure that we are not missing anything there. On Wednesday, September 23, 2020 at 12:01:46 PM UTC-5

Re: How do you set java options for ssh agents

The jvmOptions settings work, I just tested it on the latest version. Did you disconnect and connect the agent again to apply the changes? if you only click on save the agent does not discconect and connect with the new settings, you have to disconnect the agent with the action disconnect from

Re: How do you set java options for ssh agents

How much memory those agents have? you set "-Xmx64g -Xms64g" for the remoting process (not for builds) you agent has to have more than 64GB of RAM to run any build on it, you grab 64GB only for the remoting process, and this RAM should be enough to run you builds. The remoting agent usually

How do you set java options for ssh agents

I'm using ssh-slaves-plugin to configure and launch 2 ssh agents, and I've specified several java options in these agents' config (see photo and text list below), but when these agents are launched, the agents' log still shows empty jvmOptions in