Re: mailer release?

Thanks mate :) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit

Re: Plugin site prototype

+1 to that. I would love to filter out plugins that aren't directly feature enabling. At the moment, we lack any sort of metadata to make that distinction, but I think that would help the site greatly. I think it would also be good to mark those OSS Jenkins is recommends during the install

Re: Plugin site prototype

(replies inline) On Thu, 01 Sep 2016, Gus Reiber wrote: > Tyler, I am confused by your post. > 256 is A LOT less than 50k. A LOT, A LOT less. 20x less. > 10K is a lot less than 50k, so if anything, Open-Stack Cloud's 256 installs > is being exaggerated. It is being graded on an easier scale

[ANN]: Contributor Summit - Tuesday Sept 13 @ Santa Clara Convention Center

Hello, In the past couple of months the events team has been planning a Jenkins Contributor Summit at Jenkins World . This is very similar to past summits held after the Jenkins User Conferences. This year’s focus areas are: Blue Ocean, Pipeline, and

Repo Owner Permission

Hi, This project is no longer being maintained by the original owners. Could i please take over the project? I have some pending changes but there is no one maintaining it or accepting pull requests. I would like to commit and make future modifications to the project. Repo:

Re: LTS Backporting process documented

+100 /B On Thu, Sep 1, 2016 at 12:42 PM, Oliver Gondža wrote: > Finally, I manged to put a small document[1] together demystifying what > exactly needs to be done to keep LTS running. It should be enough for > people to understand what is done and how. The process currently

Re: Adding pipeline compatabilty to jenkins plugin

Saw that, but I couldn't find what you've said about the Flow Node... I guess I'll look at the code. On Thu, Sep 1, 2016 at 1:54 PM, Jesse Glick wrote: > https://github.com/jenkinsci/workflow-step-api-plugin/blob/ > master/README.md has some information though it probably

Re: Adding pipeline compatabilty to jenkins plugin

On Thu, Sep 1, 2016 at 1:54 PM, Jesse Glick wrote: > https://github.com/jenkinsci/workflow-step-api-plugin/blob/ > master/README.md has some information though it probably needs more. > https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md is > the landing

Re: Plugin site prototype

Your example highlights an issue: there is no reason to show `structs` to a user at all, since it offers no user-level features. It is just an API. No one chose to install it, they just got it as a dependency from some update of another plugin. When I worked on NetBeans we could mark modules as

Re: Adding pipeline compatabilty to jenkins plugin

https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md has some information though it probably needs more. https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md is the landing page. -- You received this message because you are subscribed to the Google Groups

LTS Backporting process documented

Finally, I manged to put a small document[1] together demystifying what exactly needs to be done to keep LTS running. It should be enough for people to understand what is done and how. The process currently is semi-automated encouraging the maintainer to review all important steps. I am

Re: mailer release?

James, I'll take a look at it and perform the release. Andrés On Thu, Sep 1, 2016 at 5:49 AM, James Dumay wrote: > It would be also great if someone could volunteer to give it a quick test > > On Thursday, September 1, 2016 at 1:32:37 PM UTC+10, James Dumay wrote: >> >>

Re: Plugin site prototype

Tyler, I am confused by your post. 256 is A LOT less than 50k. A LOT, A LOT less. 20x less. 10K is a lot less than 50k, so if anything, Open-Stack Cloud's 256 installs is being exaggerated. It is being graded on an easier scale than Structs, which is also being graded on an easier scale than

Recent changes takes too long in jenkins 2.7.1 version

Hi, We have migrated recently to Jenkins 1.603 to jenkins 2.7.1 stable version. After migration, Jenkins takes too long for displaying the changes of the current job (approx. 15min). Can you please provide me some suggestions to improve the speed? I have tried increasing log levels for git