Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugins can contribute additional commands to Jenkins CLI which, since Jenkins 1.445, will also be available via Jenkins SSH.

This is useful for (1) exposing administrative commands to admins, so that they can script some of the Jenkins babysitting work, and (2) exposing data and operations to builds executing inside Jenkins, so that they can interact with Jenkins in a richer way.

Writing commands can be done in two ways.

By putting CLIMethod on methods of your model objects

If you are exposing behaviors of your model objects as CLI commands, the easiest way to achieve it is to put @CLIMethod on a method of your model object. See Queue.clear() as an example. In addition to the command name as specified in the annotation, you also need to define "CLI.command-name.shortDescription" as a message resource, which captures one line human-readable explanation of the command (see CLICommand.getShortDescription()).

public class AbstractItem {
    public synchronized void delete() throws IOException, InterruptedException {

        if(this instanceof TopLevelItem)


Notice that the method is an instance method. So when the delete-job command is executed, which job is deleted? To resolve this, you also need to define a "CLI resolver", which uses a portion of arguments and options to determine the instance object that receives a method call.

public static AbstractItem resolveForCLI(
        @Argument(required=true,metaVar="NAME",usage="Job name") String name) throws CmdLineException {
    AbstractItem item = Hudson.getInstance().getItemByFullName(name, AbstractItem.class);
    if (item==null)
        throw new CmdLineException(null,"No such job exists:"+name);
    return item;

Of all the resolver methods that are discovered, Jenkins picks the one that returns the best return type. It doesn't matter where the resolver method is defined, or how it's named.

Both resolver methods and CLI methods can have any number of args4j annotations, which causes the parameters and arguments to be injected upon a method invocation. All the other unannotated parameters receive null. Combined with the stapler method binding, this enables you to make your method invokable from both CLI and HTTP.

By extending CLICommand

You can also implement a CLI commmand as a subtype of CLICommand, and put @Extension. You can use existing implementations in the core, such as GroovyCommand, as a starting point. CLICommand exposes a lower-level control of the CLI set up (such as a Channel.)

This approach is suitable for the commands that require more serious terminal interaction and remote code execution.

See the javadoc of CLICommand for more details.

  • No labels


  1. Unknown User (papaminos)

    Please provide some examples of CLI usage.

    Some methods are obvious, other are not. 

    For example how should i pass parameters for job when i'm trying to run it ???? 

    CLI says  


    -p     : Specify the build parameters in the key=value format.


    What if there is a number of build params?

  2. Unknown User (paulmdavies)

    This example is unhelpful, since it doesn't compile.

    The line:

    AbstractItem item = Hudson.getInstance().getItemByFullName(name, AbstractItem.class);

    doesn't compile - it says:

    Bound mismatch: The generic method getItemByFullName(String, Class<T>) of type Jenkins is not applicable for the arguments (String, Class<AbstractItem>). The inferred type AbstractItem is not a valid substitute for the bounded parameter <T extends Item>

    Since this seems to be the only example of how to do this on the internet, it would be helpful if it worked. Also, the choice of AbstractItem as the class name is a poor one, since the Jenkins code already contains a class with that name, which makes this example even more confusing.