On Saturday, December 4, 2021 at 7:25:03 AM UTC-7 senthilkumar wrote:
> 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. > 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 -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/66321260-c1e1-4248-982c-d281426fbc11n%40googlegroups.com.
