patternMinor
Load Balancing of Jenkins Nodes without Load Balancing Plugin?
Viewed 0 times
withoutnodesjenkinspluginbalancingload
Problem
we currently want to introduce a loadbalancing on the Jenkins server and our nodes. I have already created several nodes.
Currently it is also so that if a node is blocked accordingly, that the next free option is chosen. But only if a node is issued. Unfortunately, this is only part of what the whole task looks like.
Task to be solved:
-
If a node is under load, the next free option should be selected automatically.
-
If a node is issued, then the next inactive node should be taken.
Problem:
For security reasons, you do not want us to use the loadbalancing plugin. So there has to be a solution that we have through a script or some other solution
Currently it is also so that if a node is blocked accordingly, that the next free option is chosen. But only if a node is issued. Unfortunately, this is only part of what the whole task looks like.
Task to be solved:
-
If a node is under load, the next free option should be selected automatically.
-
If a node is issued, then the next inactive node should be taken.
Problem:
For security reasons, you do not want us to use the loadbalancing plugin. So there has to be a solution that we have through a script or some other solution
Solution
This is similar to:
https://stackoverflow.com/questions/55023570/how-to-run-a-job-on-first-available-node/55567958
Have you considered Least Load plugin?
https://plugins.jenkins.io/leastload
By default Jenkins tries to allocate a jobs to the last node is was executed on. This can result in nodes being left idle while other nodes are overloaded. This plugin overrides the default behavior and assigns jobs to nodes with the least load.
Don't imagine there's a security issue there.
https://stackoverflow.com/questions/55023570/how-to-run-a-job-on-first-available-node/55567958
Have you considered Least Load plugin?
https://plugins.jenkins.io/leastload
By default Jenkins tries to allocate a jobs to the last node is was executed on. This can result in nodes being left idle while other nodes are overloaded. This plugin overrides the default behavior and assigns jobs to nodes with the least load.
Don't imagine there's a security issue there.
Context
StackExchange DevOps Q#6827, answer score: 1
Revisions (0)
No revisions yet.