> Am 21.12.2017 um 15:40 schrieb Jesse Glick :
>
> On Wed, Dec 20, 2017 at 4:05 PM, Jesse Glick wrote:
>>> Preferrably without
>>> some UI, I am trying to keep things simple.
>>
>> `GlobalConfiguration`
Since your plugin is related to the static
On Wed, Dec 20, 2017 at 4:05 PM, Jesse Glick wrote:
>> Preferrably without
>> some UI, I am trying to keep things simple.
>
> `GlobalConfiguration`
BTW
https://github.com/jenkinsci/archetypes/blob/master/README.md#usage
--
You received this message because you are
> On 20. Dec 2017, at 20:04, Jochen Wiedmann wrote:
>
> No annotations, or something like that?
https://jenkins.io/doc/developer/extensibility/ explains this and links to
relevant Javadoc (the developer docs on jenkins.io are work in
not-much-progress, but this is
On Wed, Dec 20, 2017 at 2:04 PM, Jochen Wiedmann
wrote:
> My plugin A is designed to provide an extension for an extension point,
> which is defined by plugin B (existing).
> - My understanding is, that I simply create a subclass of the extension
> point class, which in
Hi,
I'd like to create a Jenkins plugin. However, I have some questions,
hopefully you are able to help me with:
- My plugin A is designed to provide an extension for an extension point,
which is defined by plugin B (existing).
- My understanding is, that I simply create a subclass of the