Master issue after LTS 2.319.1

[Senthil Ak]

Hi Team,

After the upgrade Jenkins is suggesting two things, the master node is changed to built-in and you can't run jobs on the master node. 

This is not an issue when we have a bigger Jenkins environment, like one master and multiple agents. But the issue comes when we have a small footprint. For example, we have a couple of Jenkins environments where we have only one master(inbuilt node now) and less than 10 jobs. How we can modify this to comply with the latest security changes?

- Have one master and run all jobs?

- Have one master with zero executors and have one agent on the same machine?

- Have one master and one agent on different VM or machines? - This way we are increasing the footprints.

Thanks

Senthil

[Mark Waite]

Please use 'controller' rather than 'master'.  It's more inclusive.

A controller with zero executors and an agent on the same machine is likely the best "small footprint" approach of the three you offered.   Use a separate account for the agent process and use file system permissions to prevent the agent process from reading the contents of the JENKINS_HOME directory.

Mark Waite

[Senthil Ak]

Thanks for the reply. 

Do you have any links which suggest running controller and agent on the same machine? whatever I searched I am getting only two VM instructions. It will be great if you could point me to the correct documents. 

Appreciate your response.

[Mark Waite]

On Sunday, December 5, 2021 at 1:37:51 PM UTC-7 senthilkum kear wrote:

 

Do you have any links which suggest running controller and agent on the same machine? whatever I searched I am getting only two VM instructions. It will be great if you could point me to the correct documents. 

Appreciate your response.

Same virtual machine is not significantly different from multiple virtual machines.  Create a user account for the agent, create a private key / public on the account, add the public key to the authorized_keys file, configure the agent with the host key of the agent and with the private key of the account, and you're ready to run.