Class Messages

java.lang.Object
hudson.cli.client.Messages

@Restricted(org.kohsuke.accmod.restrictions.NoExternalUse.class) public class Messages extends Object
Generated localization support class.
  • Constructor Summary

    Constructors
    Constructor
    Description
     
  • Method Summary

    Modifier and Type
    Method
    Description
    static org.jvnet.localizer.Localizable
    Key CLI.BadAuth: The JENKINS_USER_ID and JENKINS_API_TOKEN env vars should be both set or left empty. .
    static org.jvnet.localizer.Localizable
    Key CLI.NoSuchFileExists: No such file exists: {0}.
    static org.jvnet.localizer.Localizable
    Key CLI.NoURL: Neither -s nor the JENKINS_URL env var is specified..
    static org.jvnet.localizer.Localizable
    Key CLI.Usage: Jenkins CLI Usage: java -jar jenkins-cli.jar [-s URL] command [opts...] args... Options: -s URL : the server URL (defaults to the JENKINS_URL env var) -webSocket : connect using WebSocket (the default; works well with most reverse proxies; requires Jetty) -http : use a pair of HTTP(S) connections rather than WebSocket -ssh : use SSH protocol rather than WebSocket (requires -user; SSH port must be open on server) -i KEY : SSH private key file used for authentication (for use with -ssh) -noCertificateCheck : bypass HTTPS certificate check entirely. Use with caution -noKeyAuth : do not try to load the SSH authentication private key. Conflicts with -i -user : specify user (for use with -ssh; must have registered a public key) -strictHostKey : request strict host key checking (for use with -ssh) -logger FINE : enable detailed logging from the client -auth [ USER:SECRET | @FILE ] : specify username and either password or API token (or load from them both from a file); for use with -http. Passing credentials by file is recommended. See https://www.jenkins.io/redirect/cli-http-connection-mode for more info and options. -bearer [ TOKEN | @FILE ] : specify authentication using a bearer token (or load the token from file); for use with -http. Mutually exclusive with -auth. Passing credentials by file is recommended. The available commands depend on the server. Run the ''help'' command to see the list..
    static String
    Key CLI.BadAuth: The JENKINS_USER_ID and JENKINS_API_TOKEN env vars should be both set or left empty. .
    static String
    Key CLI.NoSuchFileExists: No such file exists: {0}.
    static String
    Key CLI.NoURL: Neither -s nor the JENKINS_URL env var is specified..
    static String
    Key CLI.Usage: Jenkins CLI Usage: java -jar jenkins-cli.jar [-s URL] command [opts...] args... Options: -s URL : the server URL (defaults to the JENKINS_URL env var) -webSocket : connect using WebSocket (the default; works well with most reverse proxies; requires Jetty) -http : use a pair of HTTP(S) connections rather than WebSocket -ssh : use SSH protocol rather than WebSocket (requires -user; SSH port must be open on server) -i KEY : SSH private key file used for authentication (for use with -ssh) -noCertificateCheck : bypass HTTPS certificate check entirely. Use with caution -noKeyAuth : do not try to load the SSH authentication private key. Conflicts with -i -user : specify user (for use with -ssh; must have registered a public key) -strictHostKey : request strict host key checking (for use with -ssh) -logger FINE : enable detailed logging from the client -auth [ USER:SECRET | @FILE ] : specify username and either password or API token (or load from them both from a file); for use with -http. Passing credentials by file is recommended. See https://www.jenkins.io/redirect/cli-http-connection-mode for more info and options. -bearer [ TOKEN | @FILE ] : specify authentication using a bearer token (or load the token from file); for use with -http. Mutually exclusive with -auth. Passing credentials by file is recommended. The available commands depend on the server. Run the ''help'' command to see the list..

    Methods inherited from class java.lang.Object

    clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
  • Constructor Details

    • Messages

      public Messages()
  • Method Details

    • CLI_NoSuchFileExists

      public static String CLI_NoSuchFileExists(Object arg0)
      Key CLI.NoSuchFileExists: No such file exists: {0}.
      Parameters:
      arg0 - 1st format parameter, {0}, as String.valueOf(Object).
      Returns:
      No such file exists: {0}
    • _CLI_NoSuchFileExists

      public static org.jvnet.localizer.Localizable _CLI_NoSuchFileExists(Object arg0)
      Key CLI.NoSuchFileExists: No such file exists: {0}.
      Parameters:
      arg0 - 1st format parameter, {0}, as String.valueOf(Object).
      Returns:
      No such file exists: {0}
    • CLI_NoURL

      public static String CLI_NoURL()
      Key CLI.NoURL: Neither -s nor the JENKINS_URL env var is specified..
      Returns:
      Neither -s nor the JENKINS_URL env var is specified.
    • _CLI_NoURL

      public static org.jvnet.localizer.Localizable _CLI_NoURL()
      Key CLI.NoURL: Neither -s nor the JENKINS_URL env var is specified..
      Returns:
      Neither -s nor the JENKINS_URL env var is specified.
    • CLI_Usage

      public static String CLI_Usage()
      Key CLI.Usage: Jenkins CLI Usage: java -jar jenkins-cli.jar [-s URL] command [opts...] args... Options: -s URL : the server URL (defaults to the JENKINS_URL env var) -webSocket : connect using WebSocket (the default; works well with most reverse proxies; requires Jetty) -http : use a pair of HTTP(S) connections rather than WebSocket -ssh : use SSH protocol rather than WebSocket (requires -user; SSH port must be open on server) -i KEY : SSH private key file used for authentication (for use with -ssh) -noCertificateCheck : bypass HTTPS certificate check entirely. Use with caution -noKeyAuth : do not try to load the SSH authentication private key. Conflicts with -i -user : specify user (for use with -ssh; must have registered a public key) -strictHostKey : request strict host key checking (for use with -ssh) -logger FINE : enable detailed logging from the client -auth [ USER:SECRET | @FILE ] : specify username and either password or API token (or load from them both from a file); for use with -http. Passing credentials by file is recommended. See https://www.jenkins.io/redirect/cli-http-connection-mode for more info and options. -bearer [ TOKEN | @FILE ] : specify authentication using a bearer token (or load the token from file); for use with -http. Mutually exclusive with -auth. Passing credentials by file is recommended. The available commands depend on the server. Run the ''help'' command to see the list..
      Returns:
      Jenkins CLI Usage: java -jar jenkins-cli.jar [-s URL] command [opts...] args... Options: -s URL : the server URL (defaults to the JENKINS_URL env var) -webSocket : connect using WebSocket (the default; works well with most reverse proxies; requires Jetty) -http : use a pair of HTTP(S) connections rather than WebSocket -ssh : use SSH protocol rather than WebSocket (requires -user; SSH port must be open on server) -i KEY : SSH private key file used for authentication (for use with -ssh) -noCertificateCheck : bypass HTTPS certificate check entirely. Use with caution -noKeyAuth : do not try to load the SSH authentication private key. Conflicts with -i -user : specify user (for use with -ssh; must have registered a public key) -strictHostKey : request strict host key checking (for use with -ssh) -logger FINE : enable detailed logging from the client -auth [ USER:SECRET | @FILE ] : specify username and either password or API token (or load from them both from a file); for use with -http. Passing credentials by file is recommended. See https://www.jenkins.io/redirect/cli-http-connection-mode for more info and options. -bearer [ TOKEN | @FILE ] : specify authentication using a bearer token (or load the token from file); for use with -http. Mutually exclusive with -auth. Passing credentials by file is recommended. The available commands depend on the server. Run the ''help'' command to see the list.
    • _CLI_Usage

      public static org.jvnet.localizer.Localizable _CLI_Usage()
      Key CLI.Usage: Jenkins CLI Usage: java -jar jenkins-cli.jar [-s URL] command [opts...] args... Options: -s URL : the server URL (defaults to the JENKINS_URL env var) -webSocket : connect using WebSocket (the default; works well with most reverse proxies; requires Jetty) -http : use a pair of HTTP(S) connections rather than WebSocket -ssh : use SSH protocol rather than WebSocket (requires -user; SSH port must be open on server) -i KEY : SSH private key file used for authentication (for use with -ssh) -noCertificateCheck : bypass HTTPS certificate check entirely. Use with caution -noKeyAuth : do not try to load the SSH authentication private key. Conflicts with -i -user : specify user (for use with -ssh; must have registered a public key) -strictHostKey : request strict host key checking (for use with -ssh) -logger FINE : enable detailed logging from the client -auth [ USER:SECRET | @FILE ] : specify username and either password or API token (or load from them both from a file); for use with -http. Passing credentials by file is recommended. See https://www.jenkins.io/redirect/cli-http-connection-mode for more info and options. -bearer [ TOKEN | @FILE ] : specify authentication using a bearer token (or load the token from file); for use with -http. Mutually exclusive with -auth. Passing credentials by file is recommended. The available commands depend on the server. Run the ''help'' command to see the list..
      Returns:
      Jenkins CLI Usage: java -jar jenkins-cli.jar [-s URL] command [opts...] args... Options: -s URL : the server URL (defaults to the JENKINS_URL env var) -webSocket : connect using WebSocket (the default; works well with most reverse proxies; requires Jetty) -http : use a pair of HTTP(S) connections rather than WebSocket -ssh : use SSH protocol rather than WebSocket (requires -user; SSH port must be open on server) -i KEY : SSH private key file used for authentication (for use with -ssh) -noCertificateCheck : bypass HTTPS certificate check entirely. Use with caution -noKeyAuth : do not try to load the SSH authentication private key. Conflicts with -i -user : specify user (for use with -ssh; must have registered a public key) -strictHostKey : request strict host key checking (for use with -ssh) -logger FINE : enable detailed logging from the client -auth [ USER:SECRET | @FILE ] : specify username and either password or API token (or load from them both from a file); for use with -http. Passing credentials by file is recommended. See https://www.jenkins.io/redirect/cli-http-connection-mode for more info and options. -bearer [ TOKEN | @FILE ] : specify authentication using a bearer token (or load the token from file); for use with -http. Mutually exclusive with -auth. Passing credentials by file is recommended. The available commands depend on the server. Run the ''help'' command to see the list.
    • CLI_BadAuth

      public static String CLI_BadAuth()
      Key CLI.BadAuth: The JENKINS_USER_ID and JENKINS_API_TOKEN env vars should be both set or left empty. .
      Returns:
      The JENKINS_USER_ID and JENKINS_API_TOKEN env vars should be both set or left empty.
    • _CLI_BadAuth

      public static org.jvnet.localizer.Localizable _CLI_BadAuth()
      Key CLI.BadAuth: The JENKINS_USER_ID and JENKINS_API_TOKEN env vars should be both set or left empty. .
      Returns:
      The JENKINS_USER_ID and JENKINS_API_TOKEN env vars should be both set or left empty.