Extensions Index. Jenkins defines extension points, which are interfaces or abstract classes that model an aspect of its behavior. Those interfaces define ...
Missing: /url | Show results with:/url
Plugins may want to contribute additional restrictions on the use of specific labels for specific projects. This extension point allows such restrictions.
Sometimes plugin maintainers move on without marking plugins for adoption, due to various reasons. In such case we can transfer ownership for plugins being ...
Missing: /url | Show results with:/url
The Jenkins project hosts a Jenkins instance to perform continuous integration builds for plugins. We recommend you set up CI builds for your plugin in the ...
Jenkins defines extension points, which are interfaces or abstract classes that model an aspect of its behavior. Those interfaces define contracts of what ...
First, create a class called HelloWorldAction in the same package as HelloWorldBuilder . That class needs to implement Action. Actions are a basic building ...
Missing: ownership/ | Show results with:ownership/
Extension points accessible via metastep. Several common types of plugin features @Extension s can be invoked from a Pipeline script without any special plugin ...
Missing: /url ownership/
As of version 2.7 of the Pipeline: Shared Groovy Libraries plugin, there is a new option for loading (non-implicit) libraries in a script: a library step that ...
If a user only has the Extended Read permission, the secret is simply removed from output. A more advanced option is to integrate with Credentials Plugin. See ...
Missing: /url ownership/
See the developer documentation. Path prefixes providing access to all URLs implemented in extension lists of all extension points implemented in Jenkins.