Create extension based on plugin logic

Hi, I would like to create an automated process for adding users and roles to Jenkins. However, the user management is done by the Role-Strategy Plugin ( https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin). My question is: How can I create a new plugin which depends on the source

Help releasing plugin

I've unsuccessfully tried to release our plugin. The release:prepare release:perform, seemed to go well, but I can't see the update in either of the sites mentioned or the jsonhttps://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins . The output of the release says it was uploaded to:

Build Step wrapper

Hello guys, As far as I know there is no Build-Step Wrapper/Decorator in jenkins-core,I tried (a couple month ago) to study this point but i requires some core-updates. I've got some use cases which can take advantage of this extension point. In a Job configuration we can't add some details

Re: Maven JVM terminated unexpectedly with exit code 134

Hello once again, Should I report bug about that? Br, Alexander On 10 September 2012 12:02, Alexander Potapov outro...@gmail.com wrote: Hello, Haven't seen this problem when I had one build process. Thus, we cannot take into account the case of one Maven process for sure. In my setup I

Re: Help releasing plugin

10x for your reply. It seems that it took just about a day. https://wiki.jenkins-ci.org/display/JENKINS/BlazeMeter+Plugin May I ask for a bit more direction? How do I make the wiki show the link to the .hpi itself so that people won't have to compile the code for themselves? Do I have to link to

Re: Plugin Information on Wiki shows wrong SCM

Kohsuke pointed out the root cause of my problem: Jenkow is a multi-module Maven project. The plugin project is just a sub-module. Only the main POM had the correct SCM element, but not the plugin sub-module. After adding the correct SCM element to the plugin sub-module, the Wiki macro shows

Re: Checkbox to allow the Custom Workspace be shared among different slaves.

The @N notation I was referring to was just the style of path you cited in your first scenario: job1 - /Nodes/path/job job2 - /Nodes/path/job@2 job3 - /Nodes/path/job@3 The @2 and @3 were added by Jenkins because you configured concurrent builds. I think you're actually describing two

Re: Maven Projects with dependencies is too eager since 1.481

+1 2012/9/24 Arnaud Héritier aherit...@gmail.com: Hi, +1000 with Larry I also noticed this issue triggering many many useless builds between projects. I was also suspecting this change as the root cause of the issue. Is there already an issue opened about this regression ? I'm

Diskspace Notification for Jenkins

Hi Guys, Just sharing a temporary solution for Diskspace Notifcation for Jenkins: https://issues.jenkins-ci.org/browse/JENKINS-15278 Thanks.

Archetypal plugins examples

I'm working on my slides for JUC SF, Getting to your third plugin, and in the talk I'd like to highlight some ideal plugins to fork or just to look at in general. *What would people consider ideal modern plugins?* For example while the FindBugs plugins is great, but it leans really heavily on