Agents manage the task execution on behalf of the Jenkins controller by using executors. An agent is a small (170KB single jar) Java client process that ...
It allows us to use different environments for each build project balancing the workload among multiple agents running jobs in parallel. The Jenkins controller ...
Random: The TCP port is chosen at random to avoid collisions on the Jenkins controller. The downside to randomized ports is that they are chosen during the ...
The Jenkins WAR file bundles Winstone, a Jetty servlet container wrapper, and can be started on any operating system or platform with a version of Java ...
Missing: access- | Show results with:access-
The command line interface can be accessed over SSH or with the Jenkins CLI client, a .jar file distributed with Jenkins. This document assumes Jenkins 2.54 or ...
Jenkins provides two methods for installing plugins on the controller: Using the "Plugin Manager" in the web UI. Using the Jenkins CLI install-plugin command.
The Manage Jenkins >> System Information page provides detailed information about what is available on this Jenkins instance: System Properties that can be used ...
Administrators and privileged users modify the global configuration from the Jenkins configuration pages. Jenkins home directory. The JENKINS_HOME directory is ...
Missing: /url | Show results with:/url
Setting environment variables. Setting an environment variable within a Jenkins Pipeline is accomplished differently depending on whether Declarative or ...
(The URL $root/me/configure is a good shortcut.) You can also change your API token from here. Note that Jenkins does not do any authorization negotiation. i.e. ...
Missing: control/ | Show results with:control/