Jenkins 2.0 offers command-line control. Users often use the command-line and are forced to type a lot of repetitive parameters that make the command-line long and bulky.

I would suggest to have jenkins-cli take all parameters from a configuration file that is property file or better yet a YAML file that is on the current directory or another directory (-config ....). All parameters should be readable from this configuration file FIRST and the command-line options can OVERRIDE these parameters, if needed. This would go a long way to reduced the repetitive typing of parameters for the jenkins command-line. That's the smartest and most logical way of doing things.