In a distributed builds environment, the Jenkins controller will use its resources to only handle HTTP requests and manage the build environment. Actual ...
hudson.model.Slave.workspaceRoot. tuning ... Control a agent based on a schedule. hudson.scm ... true to disable Jenkins CLI via JNLP and HTTP (SSHD can still be ...
Missing: mac | Show results with:mac
Graphs now scale correctly on high resolution screens. ... slave-agent. ... Enable Remoting work directories by default for newly created agents launched via JNLP ( ...
Specifying 4 makes Hudson schedule your builds to only run on a slave with 4 or more executors, and if your build is then run on a slave with 5 executors, the ...
Missing: distribution scalability
The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps ...
Missing: scalability | Show results with:scalability
Launching slave.jar from from console · Launch Java Web Start slave agent via Windows Scheduler · Logging · Logger Configuration · Managing Jenkins Meta-Cluster.
Missing: high | Show results with:high
... slave-agent.jnlp file. It was causing harmless ... JNLP agents are now handled through NIO-based remoting channels for better scalability. ... Added a scheduled ...
Start JNLP slave ignores jar-cache flag (issue 20093); Too many open files upon HTTP listener init or shutdown (issue 14336); Extension point for secure users ...
Missing: distribution | Show results with:distribution
In order to show you the most relevant results, we have omitted some entries very similar to the 8 already displayed.
If you like, you can repeat the search with the omitted results included. |
