Make all CLI commands compatible with Pipeline where possible (#2874)
* [FIX JENKINS-30785] Generalize some CLI stuff to AbstractItem * Offering default methods on ParameterizedJob. * Javadoc typo. * Cleaner use of default methods in ParameterizedJob. * Need to pick up https://github.com/infradna/bridge-method-injector/pull/15 to be able to build. * Sketch of pulling disabled functionality into ParameterizedJob. * EnableJobCommandTest.groovy → EnableJobCommandTest.java, and replacing deprecated Remoting-based CLI calls with CLICommandInvoker. * All CLI commands could be broken by a missing CLI.*.shortDescription key on just one! * Forgot to move CLI method short descriptions to new package. * Needed a @CLIResolver for ParameterizedJob. Adding an OptionHandler while we are here. * Trying to fix up access-modifier versions; started failing in CI today for unknown reasons. * Introduced <p:makeDisabled/> by analogy with <p:config-disableBuild/>. * Using new type bounds. * access-modifier 1.11 released. * MatrixProject and MavenModuleSet both expect to have access to makeDisabled.jelly. * Trying to generalize some more. * Minor simplification. * [JENKINS-34716] Generalizing doPolling and schedulePolling. * isBuildable * Obsolete comment. * Updated comments. * bridge-method-injector 1.17 * Unfortunately AbstractProject.schedulePolling cannot delegate to SCMTriggerItem. * Making delete-builds and list-changes commands work with Pipeline. * [FIXED JENKINS-41527] Made console CLI command compatible with Pipeline. * Fixed set-build-description and set-build-display-name. * @oleg-nenashev agreed it would be clearer to explicitly mark commands as restricted, not APIs. * Updated tests to match slight message changes. * bridge-method-injector 1.17 * @olivergondza pointed out that RunRangeCommand is a better name than JobRangeCommand.
Please register or sign in to comment