hudson.remoting.jnlp.Main
.
-
+Container image (repository, name, and tag) for a Jenkins inbound agent.
+Connection details will be passed as environment variables as per
+documentation.
diff --git a/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/ContainerTemplate/help-name.html b/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/ContainerTemplate/help-name.html
index 3029029eb2..3009bc9847 100644
--- a/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/ContainerTemplate/help-name.html
+++ b/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/ContainerTemplate/help-name.html
@@ -1,5 +1,5 @@
The name for the container to be run.
-One container is automatically created with name jnlp
, and runs the Jenkins JNLP agent service.
+One container is automatically created with the name jnlp
, and runs the Jenkins agent.
-In order to replace the default JNLP agent, the name of the container with the custom JNLP image must be jnlp
.
+In order to replace the default agent image, the container with the agent must be named jnlp
.
diff --git a/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud/config.jelly b/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud/config.jelly
index 69aaabf1d1..f8e4865a76 100644
--- a/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud/config.jelly
+++ b/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud/config.jelly
@@ -46,11 +46,11 @@ THE SOFTWARE.
With this option it is possible to connect directly to the TCP agent listener port. - This skips the connect to an HTTP(S) port to retrieve the connection information. + This skips the connection to an HTTP(S) port to retrieve some metadata.
This is useful in scenarios where the controller does not expose an HTTP(S) port, for example - Jenkinsfile Runner. -
- -- Here is an example how the connect on agent side would look like. Most parameters are provided automatically when you enable the Direct Connection option. -
- java -cp agent.jar hudson.remoting.jnlp.Main \ - -headless \ - -workDir <WORK_DIRECTORY> \ - -direct <MASTER_HOST:TCP_AGENT_LISTENER_PORT> \ - -protocols JNLP4-connect \ - -instanceIdentity <INSTANCE_IDENTITY> \ - <SECRET_STRING> <AGENT_NAME> -- - -
- You find more information in the Jenkins Remoting project. + Jenkinsfile Runner, + but more commonly if you simply wish to optimize the connection slightly.
Note: In Direct Connection mode agents will not be able to reconnect to a restarted controller if a Random 'TCP port for inbound agents' is configured!
- Note: Direct Connection requires a inbound-agent image with a version equal or higher than 3.35-5.
Note: Direct Connection does not work with the currently available jenkins/inbound-agent:windowsservercore-1809
image.
- Specify time in seconds up to which Jenkins should wait for the JNLP agent to establish a connection.
+ Specify time in seconds up to which Jenkins should wait for the agent to establish a connection.
Value must be a positive integer.
Name of the default container steps will be run in.
When using this option, all steps will be executed within an implicit container(name) {...}
block instead
- of the jnlp container.
jnlp
container.