Claim plugin maintainer?
Hi, it seems that the claim plugin has currently no maintainer, right? If so, I'd like to go ahead and fix some of the outstanding bugs/issues for the plugin. cheers Kutzi --
Re: Request for commit access to debian-package-builder
Hi, Sam! Its great to hear of your interest in that plugin! It happens that I am original developer of the thing and I'm glad to see that it found some usage? Could you please tell what are the new features you are planning to add? We are coming to the next iteration of the plugin development in a week or two so we can cooperate a bit. Also, what is your deployment environment? What are you accomplishing with the help of the plugin? Best regards, Ivan Kalinin. On Saturday, January 26, 2013 11:09:21 PM UTC+4, Sam Kottler wrote: Hi, Development seems to have become stagnant on the plugin and I'd like to work on adding some features and fixing bugs I've come across with the fairly large deployment I currently maintain. Thanks and let me know if you have any questions! -Sam --
Re: Request for commit access to debian-package-builder
Awesome, thanks for all your hard work! One of the main features I've added is the ability to use pbuilder (and pdebuild) instead of just plain debuild. This is key because I'm building around 1500 packages a day right now across dozens of slaves so having a consistent base for build chroots via pbuilder is key. There are also a few small workflow issues I've fixed that I would like to get upstream. What's the best workflow for you? I'm happy to just submit pull requests or help maintain the plugin - totally your call. Thanks again, Sam On Sun, Jan 27, 2013 at 11:35 AM, Ivan Kalinin pupss...@gmail.com wrote: Hi, Sam! Its great to hear of your interest in that plugin! It happens that I am original developer of the thing and I'm glad to see that it found some usage? Could you please tell what are the new features you are planning to add? We are coming to the next iteration of the plugin development in a week or two so we can cooperate a bit. Also, what is your deployment environment? What are you accomplishing with the help of the plugin? Best regards, Ivan Kalinin. On Saturday, January 26, 2013 11:09:21 PM UTC+4, Sam Kottler wrote: Hi, Development seems to have become stagnant on the plugin and I'd like to work on adding some features and fixing bugs I've come across with the fairly large deployment I currently maintain. Thanks and let me know if you have any questions! -Sam --
Disabling the People link or functionality?
Hi, I have had some resource consumption issues with Jenkins for a while, which I hoped would be fixed in 1.500 based on the available change log listing several people related issues to be fixed. Unfortunately accessing /asyncPeople or /people still results in fully loaded CPU and massive memory leaks. Is there any way to remove the link completely from the left-hand menu? Or disabling CVS users from automatically being added to the Jenkins user database? Thanks, David --
Re: Hosting request for new plugin
What's next? What are the steps involved to get the plugin to appear on the official list, etc. Thanks On Tuesday, 22 January 2013 08:26:08 UTC, Ullrich Hafner wrote: Hi David, Created https://github.com/jenkinsci/scala-plugin Welcome aboard! Ulli Am 21.01.2013 um 17:14 schrieb Chemmo che...@gmail.com javascript:: I thought as much, here it is: https://github.com/Chemmo/scala_plugin David On Monday, 21 January 2013 08:28:15 UTC, Ullrich Hafner wrote: Hi David, the best thing would be if you create a github project in your GitHub account. We then fork that project to the jenkins-ci organisation. Ulli Am 20.01.2013 um 23:29 schrieb Chemmo che...@gmail.com: Hi, I'd like to publish my scala plugin, which allows you to create a scala build step and enter code into a text box which is compiled and executed when the job runs. You can also specify one or more directory of jars which will be appended to the classpath at runtime. My git username is Chemmo. Is there anything else you need to know? :) Thanks David --
Re: Disabling the People link or functionality?
Not sure on disabling the feature, but I've had a look at fixing the underlying slow performance: * The incremental code calls getBuilds().size() for the progress calculation, which seems to eager-load all builds in a job. Those builds will currently be loaded anyway eventually, but if you have a lot of old builds, this breaks the cancellation check and a lot of the responsiveness of the async approach. This would be easy to fix (e.g. just guess 100 builds)... * I've also been looking at introducing a persistent cache and caching getLastUnstableBuild etc; I got good results from applying caching to the People view. I've been making some comments on the getLastUnstableBuild bug: https://issues.jenkins-ci.org/browse/JENKINS-16089 The branch I've been working on: https://github.com/justinsb/jenkins/commit/caching I think the caching approach is promising, but I'd welcome any comments on the idea/approach! Justin On Sun, Jan 27, 2013 at 10:05 AM, David Kovalev Langeland helten...@gmail.com wrote: Hi, I have had some resource consumption issues with Jenkins for a while, which I hoped would be fixed in 1.500 based on the available change log listing several people related issues to be fixed. Unfortunately accessing /asyncPeople or /people still results in fully loaded CPU and massive memory leaks. Is there any way to remove the link completely from the left-hand menu? Or disabling CVS users from automatically being added to the Jenkins user database? Thanks, David --
Re: Hosting request for new plugin
Could someone set up a CI build of my plugin? I also tried to release with: mvn release:prepare release:perform -Dusername=... -Dpassword=... but I get this error: [ERROR] Non-resolvable parent POM: Could not find artifact org.jenkins-ci.pl ugins:plugin:pom:1.447 in central (http://repo.maven.apache.org/maven2) and 'par ent.relativePath' points at wrong local POM @ line 3, column 11 - [Help 2] There isn't anything relating to 1.447 in the hosting plugins wiki page? Thanks On Tuesday, 22 January 2013 08:26:08 UTC, Ullrich Hafner wrote: Hi David, Created https://github.com/jenkinsci/scala-plugin Welcome aboard! Ulli Am 21.01.2013 um 17:14 schrieb Chemmo che...@gmail.com javascript:: I thought as much, here it is: https://github.com/Chemmo/scala_plugin David On Monday, 21 January 2013 08:28:15 UTC, Ullrich Hafner wrote: Hi David, the best thing would be if you create a github project in your GitHub account. We then fork that project to the jenkins-ci organisation. Ulli Am 20.01.2013 um 23:29 schrieb Chemmo che...@gmail.com: Hi, I'd like to publish my scala plugin, which allows you to create a scala build step and enter code into a text box which is compiled and executed when the job runs. You can also specify one or more directory of jars which will be appended to the classpath at runtime. My git username is Chemmo. Is there anything else you need to know? :) Thanks David --
Request to Add new plugin
Hi I would like to request hosting for my plugin which currently resides here https://github.com/suryagaddipati/slave-utilization-plugin Let me know if I need to submit any other info about the plugin/hosting. --
Re: Another LTS release needed
Hi, backports are done, build passes without failures [1]. Could you please release RC for manual testing? Thanks Vojta [1] https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_lts_branch/85/ On Tuesday 22 January 2013 10:50:51 Kohsuke Kawaguchi wrote: There were a number of fall-out issues after SECURITY-49. As Jesse found out, some of them are pretty bad, such as JENKINS-16319 and JENKINS-16278. So I think we need to release 1.480.3. Any other issues that we need to backport? -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group, send email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
