• J
    [JENKINS-27299] Define disabled in ParameterizedJob rather than AbstractProject (#2866) · 3af0cc68
    Jesse Glick 提交于
    * 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.
    
    * bridge-method-injector 1.17
    3af0cc68
pom.xml 29.7 KB