Re: Seeking new lead maintainer for the GitLab plugin

> On 13.12.2016, at 20:45, Owen B. Mehegan wrote: > > We are seeking new maintainers for the GitLab plugin! The existing codebase > is clean and well-tested thanks to a lot of hard work done by Robin, the > former lead maintainer, but he is no longer using GitLab and

Re: Django build is taking too much time to build through jenkins . How to deploy same build on multiple servers ?

This list is for discussing development of Jenkins core and its plugins. You should ask your question on the Jenkins Users list: https://groups.google.com/forum/#!forum/jenkinsci-users On Monday, December 12, 2016 at 1:08:34 AM UTC-8, sidhartha kumar Mahato wrote: > > I have the following

Best practices for synchronizing access to Item data

I am working on a plugin that needs to modify filesystem data that is associated with an Item. This modification will occur during builds of that Item possibly in parallel. My first attempt was to just synchronize on the Item itself but that seems to be too coarse grained as the UI locks up

Seeking new lead maintainer for the GitLab plugin

We are seeking new maintainers for the GitLab plugin! The existing codebase is clean and well-tested thanks to a lot of hard work done by Robin, the former lead maintainer, but he is no longer using GitLab and does not have spare time to keep working on the plugin. We're looking for an active

Re: Making a plugin with the same hudson.task.Builder and hudson.task.Publisher implementation

Okay, I was hoping there was some BuilderPublisher class I could just extend :) I'll go copy-pasta route. Thanks! On Monday, December 12, 2016 at 12:36:43 PM UTC-7, Kanstantsin Shautsou wrote: > > Unfortunately freestyle build is not freestyle. I guess because of > workflow nobody interested

Re: What should we do with the CLI?

On Mon, Dec 12, 2016 at 11:03 PM, Daniel Beck wrote: > Only allow authenticated use? Well the problems in these cases related to vulnerabilities in the Remoting layer preceding the check for authentication. We could probably make this safer by using a whitelist during the

Re: Update JDK version to 1.8 for xldeploy-plugin

On Tue, Dec 13, 2016 at 6:53 AM, Himanshu Taneja wrote: > Our build is configured to run on JDK 1.7 currently. Due to which > the new 1.8 codebase doesn’t build. Could you please reconfigure our gradle > build job to run on 1.8? > > Build job:

Re: Wiki page for plugin is not updating

Hi Daniel, thanks for the hint. I renamed it back. Hopefully it will work ;) Sorry for my silly question. It's my first jenkins plugin ... Am Dienstag, 13. Dezember 2016 14:52:22 UTC+1 schrieb Daniel Beck: > > > > On 13.12.2016, at 09:00, Martin Reinhardt > wrote: > >

Re: Wiki page for plugin is not updating

> On 13.12.2016, at 09:00, Martin Reinhardt wrote: > > I've releases my rocket chat plugin successfully to the stable channel > (rocketchatnotifier.hpi). But the wiki page doesn't show more infos: > https://wiki.jenkins-ci.org/display/JENKINS/RocketChat+Plugin. Any

Update JDK version to 1.8 for xldeploy-plugin

Hi Folks, We have a jenkins plugin built on cloudbees. And we have recently moved to JDK 1.8. Our build is configured to run on JDK 1.7 currently. Due to which the new 1.8 codebase doesn’t build. Could you please reconfigure our gradle build job to run on 1.8? Please let me know, if there is

Re: What should we do with the CLI?

On 13 December 2016 at 17:03, Daniel Beck wrote: > Hi everyone, > > We've now had not one, but two unauthenticated remote code execution > vulnerabilities in Jenkins: > > - SECURITY-218 in > https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 > -

Wiki page for plugin is not updating

I've releases my rocket chat plugin successfully to the stable channel (rocketchatnotifier.hpi ). But the wiki page doesn't show more infos: